Extensible language system (via INI files) What is the naming convention for the .ini file? For example, in Simplified Chinese
The name of the .ini file isn't important; you can give it any name you want. However, there's a line 116 in the .ini file where you need to enter the name of the language you want to translate into. Although the .ini file name isn't crucial, if you want the added languages to be automatically recognized by Windows, it's best to name the file using an international language code (e.g., tr, en, de, fr, ru, etc.).
Ty for this tool, however I have 1 question pls. Why does this small tools take several seconds to start?
The initial startup process may take 2-3 seconds because it performs several checks in the background, such as checking disk size, administrator privileges, and operating system language.
Looks to be on point no BS tool, hope it gets added to Sergei Strelec WinPe soon. Thank you very much for making it available.
hello specialist in system restoration can see to modify certain parameters thank you for the integration of wimlib there is no WinRE recovery partition of 1024 MB either it and in c: recovery folder but I prefer to have it in a separate partition not in c can create errors when resetting the pc! modify disk part available for partitions be able to create its recovery partition on the usb key disk or other rescue disk I do this on my PCs I insert two disks one for Windows and the other my system backup on the second disk I create a partition in fat 32 if I am in uefi I install the Windows boot programs except sources which is on another ntfs partition my script automatically searches install.wim I can create my partition as I want or on windows backup tools v2 it has no recovery 1024 WinRE and can create a recovery partition to store install.wim can you study this request thank you again for your work sorry google transtale informing Mr ERTURK
I've received feedback that this application doesn't work on some custom WinPE systems, like those of Sergei Strelec. First, let me state this: I recommend using pure Windows WinPE to use this application in a WinPE environment. Now, let's get to the technical explanation: On some custom modified WinPE systems, the silent crash is due to environmental limitations of WinPE itself rather than a flaw in the application's logic. Here's a summary of the environmental factors that prevent the application from starting: Missing WMI Services: Many "Lite" WinPE versions exclude the WMI (Windows Management Instrumentation) service to save space. Since the application relies on WMI to scan disks, it will crash immediately if the service isn't found. RAM Disk (X Restrictions: As a "Single File" application, it must extract local DLLs to the TEMP folder on the RAM disk. If the RAM disk is full, or if there are security policies prohibiting execution from the TEMP directory, the application cannot load its components. Modern DPI Scaling: The application uses `PerMonitorV2` DPI awareness. Basic WinPE display drivers often fail to initialize this modern graphics mode, leading to a startup error. Shell/UAC Limitations: The application may fail in WinPE environments where the built-in Administrator control (using the `runas` command), standard User Account Control (UAC), and Shell Execution services are partially disabled or reduced. Conclusion: The application is technically sound; the problem is that it requires a more "complete" WinPE environment (including WMI and sufficient RAM disk permissions) to start the .NET 8 runtime and crawl engines. Good news: v2 Sergei works in WinPE.
Migration to .NET 8 Core: The entire codebase has been migrated to .NET 8, ensuring superior performance and improved compatibility within WinPE environments. no works v3 sergei strelec WinPE environments