Skip to content

Failed to parse detected application contained a Japanese named applcation #457

Description

@terurin

I tried to install winapp, but the installing process was stopping at parse detected applications.

I report error log and my enviroment.
Applications using CKJ Font probaby will occur a parsing error.

Error log

Creating an application entry for cmd... Done!
Creating an application entry for access... Done!
Creating an application entry for excel-o365... Done!
Creating an application entry for onenote-o365... Done!
Creating an application entry for outlook-o365... Done!
Creating an application entry for powerpoint-o365... Done!
Creating an application entry for publisher-o365... Done!
Creating an application entry for word-o365... Done!
/home/teru/.local/share/winapps/detected: 行 67: 対応する ``' を探索中に予期しないファイル終了 (EOF) です
Exiting with status '1'.
  • /home/teru/.local/share/winapps/detected: 67
NAMES+=("タッチ キーボードと手書きパネル")

My enviroment

Activity

  1. pluvium27 commented on Aug 11, 2025

    @pluvium27

    same error exists in chinese version of windows 11 pro.
    log:

    正克隆到 '/home/ajax/.local/bin/winapps-src'...
    remote: Enumerating objects: 3957, done.
    remote: Counting objects: 100% (1624/1624), done.
    remote: Compressing objects: 100% (475/475), done.
    remote: Total 3957 (delta 1363), reused 1166 (delta 1145), pack-reused 2333 (from 4)
    接收对象中: 100% (3957/3957), 28.89 MiB | 7.64 MiB/s, 完成.
    处理 delta 中: 100% (1904/1904), 完成.
    Installing WinApps.
    Checking for existing conflicting WinApps installations... Done!
    Attempting to load WinApps configuration file... Done!
    Checking whether dependencies are installed... Done!
    Checking whether the user 'ajax' is part of the required groups... Done!
    Checking the status of the Windows VM... Done!
    Checking for an open RDP Port on Windows... Done!
    Attempting to establish a Remote Desktop connection with Windows... Done!
    Checking for installed Windows applications... Done!
    Creating an application entry for Windows... Done!
    Q) How would you like to handle officially supported applications? --> Skip setting up any officially supported applications
    /home/ajax/.local/share/winapps/detected: 行 94: $'\316\336\267\250\275\253ֵ\241\260System.Object[]\241\261ת\273\273Ϊ\300\340\320͡\260System.Xml.XmlDocument\241\261\241\243\264\355\316\363:\241\260\265\332': 未找到命令
    Exiting with status '127'.
    

    any countermeasures?

  2. KernelGhost commented on Sep 20, 2025

    @KernelGhost
    Member

    @terurin It looks like the setup process is running into problems with Unicode handling. Would you be able to share a download link to the Japanese application you’re using? Having access to a test application would help us reproduce the issue and work on a fix.

  3. terurin commented on Sep 23, 2025

    @terurin
    Author

    "タッチ キーボードと手書きパネル" is "Touch Keyboard and Handwriting Panel Service" in English, which is a Windows
    default application. Therefore the download link does not exist. And the application maybe appear by Windows' language settings.

  4. anmoti commented on Dec 30, 2025

    @anmoti

    This issue is also occurring in my environment.
    Is there a temporary workaround or planned fix?

    The problematic software is also “タッチ キーボードと手書きパネル”.

    The detected file is encoded in Shift-JIS (CP932).

  5. anmoti commented on Dec 30, 2025

    @anmoti

    As a temporary measure, I found that enabling the following items allows the process to proceed without issues.

    Settings > Time & language > Language & region > Administrative language settings > Change system locale, and check Beta: Use Unicode UTF-8 for worldwide language support

    https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page

  6. 0x6a6f73687561 commented on Jan 7, 2026

    @0x6a6f73687561

    Same on my Windows VM, of which locale is Korean.

    • Root Cause: The redirect from PowerShell to the Linux host does not handle non-ASCII error strings or mixed encodings gracefully, breaking the bash source command.

    • Workaround: Temporarily change the Windows Display Language to English (US), with Beta: Use Unicode UTF-8 for worldwide language support checked for the duration of the installation. Once the apps are successfully detected and the setup is complete, you can safely switch the Windows language back to your original preference (e.g., Korean). This bypasses the encoding issues entirely during the critical scanning phase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions