probably due to his kms activator (that and W11's newer restrictions) smh, remember GH is now micro****'s now
Page not found, will W7ESUi be discontinued or are there plans to continue it? Thanks in advance. _________________ home7ech Creative Learning by Doing, Slowly but Do iT Cool's
Hello, Thanks for the BypassESU-X! In BypassESU-X, why isn't the registry key Win10CommercialW365ESUEligible added directly as an option in LiveOS-Setup.cmd and Wim-Integration.cmd? This feature seems highly important and virtually mandatory. Thanks again for all your work!
The bypass is for all 1904x builds the registry only works for build 19045, and it may not continue to work
As it turned out, the problem was in one registry key value, as far as I can tell. Let me briefly recap the problem: When trying to use “OfficeScrubber” in the freshly installed Win8.1 Embedded Industry Pro (32-bit), I get the error "Input Error: There is no script engine for file extension '.vbs'." Since I turned to LLM GPT 5.1 for help in solving this problem, it provided several fixes that did not affect the error, but nevertheless, the last fix eventually helped me overcome this problem. So, I'm not sure if just one registry edit, which ultimately helped me, will be enough, so I'll add some extra steps to the instructions in the spoiler that I did before the decisive registry edit. Spoiler: Guide ◄ Quick tip for advanced users: Go to “HKEY_CLASSES_ROOT\.vbs” and change the value of the “(Default)” string from * to VBSFile. For less advanced users: Open the Registry Editor by pressing the hotkey Win + R and entering regedit in the window that just opened. Go to “HKEY_CLASSES_ROOT\.vbs”. Or, to avoid a long manual search, right-click on the “HKEY_CLASSES_ROOT” key and select Find..., then uncheck the Values and Data options and enter “.vbs” in the search field; Double-click on the line labeled “(Default)”, and then in the window that just opened, replace the * symbol with VBSFile Click “OK”. Done ✅ ⚠ If the problem still persists, then follow these steps: Open the Command Terminal with administrator rights. For example, using the hotkey Win + X; Enter the command ⤵ Code: regsvr32.exe vbscript.dll Please note that if you have a 64-bit system, you also need to enter two additional commands, namely↙ Code: cd %systemroot%\SysWOW64 regsvr32.exe vbscript.dll Enter the following 2 commands in sequence ⤵ Code: assoc .vbs=vbsfile ftype vbsfile="%SystemRoot%\System32\WScript.exe" "%1" %* Done ✅ I can say with certainty that this problem only occurs in the 32-bit edition of Win8.1 Embedded Industry Pro, as I checked for this problem in the equivalent 64-bit OS on a virtual machine. @abbodi1406 Can we expect this fix to be integrated into a future version of OfficeScrubber?
This is os specific issue or bug, related to wider system behavior (vbscript) i don't think the scrubber script should touch that
EDITED2 : Not needed for LTSC / IoT LTSC running / online ( Windows Update and DISM /Online works OOB )
All windows 10 SKUs need ESU bypass tools to be able to install/integrate updates manually. Only by WU LTSC doesn't need the ESU Bypass (this includes manually running the MSU, this also uses the WU engine).
Installing ESU LCU manually (without W10UI) in online W10 IoT Enterprise LTSC does not need BypassESU_X. Tested with november LCU KB5068781.
This was the not quoted txt where sonic replied to, the user was offline integrating updates. I didn't test manually running the msu on LTSC, i leave the online updating to WU, will test with an older ISO. EDIT: I just was informed that i was right, installing the MSU online = using the WU engine.
The keyword is Online whether installed by WU, msu, or Dism cab all on reboot, ESU validation sees that SKU is allowed and skip validation (EnterpriseS / EnterpriseSN / IoTEnterpriseS / EnterpriseG)