This code may not work correctly, for example, if script is published via the Wsus Package Publisher and executed with wuauclt.exe. Code: whoami /GROUPS | find /i "S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464" 1>nul && ( Code: whoami /GROUPS | find /i "S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464" 1>nul || goto :E_TI This code is working correctly.
Hi Cartman, you may have to try to uninstall that SSU version from 03/2023 (KB5023790) [Microsoft have a habit of adding mitigations with SSUs to counter BypassESU's installation protocols at times.] SSUs are deemed "uninstallable" (meaning "no uninstall" available), yet search on the internet for the webpage article (look closely into the information provided) on how to reverse that condition (IT CAN BE DONE, I assure you I've done it myself): windows-updates-fehlende-deinstallation-erzwingen It is an article listed on borncity.com website. Use PowerRun to assist you in uninstalling the SSU by changing some crucial details to 3 files in its installer properties with that specific KB5023790 update package. After you're done with that specific work, you can manually uninstall the SSU package. I haven't a clue yet whether the previous SSU update package (KB5022922, released on 28/02/2023 - digitally signed 12/01/2023) mitigates against BypassESU-Blue v1r. Now, I'm a Windows 8.1 Professional x86 user and I've spent my last 3 weeks testing out abbodi1406's W8-1ESUI v0.1 installer CMD script. It helped me with installing the February 2023 and March 2023 Windows Embedded 8.1 x86 Security Updates for Windows 8.1 x86 versions (it may do the same with installing updates for x64 versions too.) The best chances for success method with using W8-1ESUI v0.1 is using 7-Zip to "extract" the 4 needed files - 2x .CAB, 1x XML and 1x TXT from the .MSU update packages you downloaded from Microsoft Update Catalog (Simply copy 1 specific .MSU update package into the same folder as W8-1ESUI v0.1, right-mouse button for '7-Zip' => "extract here" for the 4 files from that .MSU update package. Once completed successfully, you can then delete only that .MSU file, because it's the .CAB files that make the home run with installing that update.) Before you begin, place that W8-1ESUI folder in an "easy to access" drive location using DOS commands (eg. c:\w81esui\ or d:\w81esui\ ). And of course, when you're ready to begin, run the W81ESUI.CMD file with Administrator privileges. If all looks good with the details presented, press "0" to start, else press "9" to exit. It's not too difficult a program to set up, usually when the above conditions are met, you're set - just press "0"). After restarting, for the next .MSU update package installation don't forget to delete those 4 files from the previous .MSU update package in the W8-1ESUI folder. BTW, with W81ESUI at least, you don't really need to change registry settings yet for EditionID, InstallationType and ProductID - you can keep them as originally set to your Windows 8.1 installed edition. You don't need the ESU Licensing Package (KB5017220) installed on the Windows 8.1 x86 version, and you don't need to be Online on the internet when installing "extract"-ed downloaded .MSU update packages. I also still use Windows 7 Ultimate x86 and x64 versions with BypassESU v12 and also abbodi1406's W7ESUI v0.4 installer CMD script. I had to use W7ESUI v0.4 to install Windows Embedded 7 Security Updates for March 2023 (When I opened the .MSU packages I got a "wrong version of Windows 7 installed" message denying me the installation, but I got around it with the 7-Zip method mentioned above. There's yet to be released a latest SSU for Windows 7 since September 2022.) You can hold off from installing the SSU released packages until when comes the month where security updates won't open the installer. It is at this time that you install one of those SSU update packages that was released months prior, but never the latest SSU update package (give abbodi1406 some time to mitigate around it for a new BypassESU release version.) abbodi1406 is a legend with his scripts for installing updates on ESU versions. ACE!!!! Any more installation problems with security updates, you'll have to use DISM to repair errors with some installed components using the commands as follows: (Open a Command Prompt window with "Run As Administrator" privileges, and you NEED TO BE ONLINE for this process) 1st attempt: dism /online /Cleanup-Image /StartComponentCleanup ** This process may take 1-12 hours pending on your computer's hardware specifications ** 2nd attempt: dism /online /Cleanup-Image /RestoreHealth ** This process may take 60-90 minutes at most ** After both attempts are completed, close the Command Prompt window. Now, open Windows Update and "Change Settings" (change to "Check for updates but let me download and install them"). Once done, select Check For Updates. You may need to reinstall update packages to some components, just be cautious for those related to Windows 10 telemetry support (un-tick and hide those updates only if you don't want them, period!) Once completed, you can try again at installing those security updates you had difficulties with. I had to do this entire process when I attempted to mitigate a custom BypassESU v12/BypassESU Blue script for installing Windows 8.1 Embedded updates using the original .MSU packages (all of them installed except the February 2023 Security Only Quality Update). Now, W8-1ESUI is currently the best performer for installing updates, as "extract"-ed packages. Good luck.
stop windows update service and delete SoftwareDistribution folder from C:\Windows\SoftwareDistribution modify registry with these value go on this key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "InstallationType"="Embedded" "EditionID"="EmbeddedIndustryE" "ProductName"="Windows Embedded 8.1 Industry Enterprise" reboot and search for news update
i'm not sure why it didn't work for you. bluebypass worked for me with kb5023790 ssu and with kb5023765 rollup on my dad's toshiba laptop running win8.1 core/home edition manually downloaded & installed both updates from ms update catalog though
Hi. I have windows 8.1 with January updates. I put in the registry: "InstallationType"="Embedded" "EditionID"="EmbeddedIndustry" "ProductName"="Windows Embedded 8 Standard" No new updates My BypassESU Blue v1 will not work. When I run LiveOS-Setup there is an error - "run any process with trustedinstaller privileges" program does not work. What to do?
Windows Embedded 8 support ends on July 11, 2023. do you plan to upgrade to windows server 2012 after that?
Hi, I can install the April cumulative update normally, but the May update (KB5026415, 2023-05) cannot be installed. Windows prompts "The update is not applicable to your computer".
Did you change EditionID to EmbeddedIndustry? it's needed for msu installation or just extract cab file and use dism.exe /Add-Package
Not working for me either this month in that Windows Updates is not presenting the option of installing the 400mb+ (or whatever) worth of May security updates for Embedded. As usual, I changed the EditionID value from Core to EmbeddedIndustry. Nevertheless, the only critical updates presented on my system are for Windows Malicious Software Removal Tool.
Your OS version is x86 (32-bit) or x64 (64-bit)? For Windows 8.1 x86 version only, it won't really be ESU supported so the ESU Licensing package provided in August 2022 is useless for BypassESU-Blue-v1r (more of a hinderance, really, I get the impression that BypassESU-Blue-v1r was conceptualized more for mitigating Windows Server 2012 R2 x64 updates for installing also into Windows 8.1 x64, as well as its own Embedded x64 updates only.) And changing the EditionID to EmbeddedIndustry in the registry didn't work out for me with installing February's .MSUs for the monthly security updates. Seems like some kind of exceptions in effect for the x86 version with displaying available new security updates in Windows Update (whether ESU or no ESU licensing in effect, and only EditionID set to EmbeddedIndustry in the registry may work for displaying new monthly security updates in Windows Update but not necessarily for installing all of them successfully.) For the sake of being able to see the available monthly security updates in Windows Update, it may require mitigating a "Win8-1_WU_ESU_Patcher" for Windows 8.1, alike the one created for Windows 7 ESU (whether it will accommodate the x86 versions may be a challenge.) Alternately, to this day the W8-1ESUI v0.1 Installer scripts have performed outstandingly with installing the security updates solely as "unpacked" files from their .MSU packages only. The method I've described twice over in responses #46 and #57 are for novice users more inclined to "click more on the mice/touchpads" than to be typing in commands in a command-prompt window (as per an individual basis, a "comfort" matter.)