Did you check the troubleshoot Q&A? abbodi1406 said: ↑ - Troubleshoot Q&A: https://forums.mydigitallife.net/posts/1583751/ Thanks for the advise, in my case it is: Q: With v5 I get error 3, The system cannot find the path specified. A: Create the folder "C:\Windows\ConfigSetRoot\" manually and put in "Windows6.1-KB4528069-x86.cab" or "Windows6.1-KB4528069-x64.cab" (x86 on 32bit -and x64 on 64bit Windows) and rerun the cmd. Created the folder, converted windows6.1-kb4528069-x64_b00bef3c3a13b8bc65bfaea63426386dbb54c336.msu to .cab with win toolkit but still it didn't work.
I have time now to work this out. I do not get notifications for new updates on all the windows 7s but one. The one was a clean installation October lat year. The rest of the 7s I have do not give notice for updates. The extended support. All windows 7s have the v5. All the computers that have 7 have the proper updates installed and only one runs flawless I can manually update but rather WU let me know. I was told to refresh or reset WU. Can someone tell me or post the link
I am sorry, I can't get it. Created: C:\Windows\ConfigSetRoot\project bin and in this folder I put the file "Windows6.1-KB4528069-x64.cab" - start LiveOS-Setup.cmd =============did not work (ERROR 3) Created: C:\Windows\ConfigSetRoot\bin and in this folder I put the file "Windows6.1-KB4528069-x64.cab" - start LiveOS-Setup.cmd =============did not work (ERROR 3) Please could you help me with more details, I know I am not a Windows 7 Pro, but trying to solve it.
Code: Q: With v5 I get error 3, The system cannot find the path specified. A: Create the folder "C:\Windows\ConfigSetRoot\" manually and put in "Windows6.1-KB4528069-x86.cab" or "Windows6.1-KB4528069-x64.cab" (x86 on 32bit -and x64 on 64bit Windows) and rerun the cmd. Just create "c:\windows\configsetroot\" and put the cab file in the folder.
I have done everything lke in the manual, created "C:\Windows\ConfigSetRoot\" manually and put in "Windows6.1-KB4528069-x64.cab" but always ERROR 3
Why don't you post your question at KUC thread... https://forums.mydigitallife.net/th...8-r2-wms-or-win-embedded-update-status.30670/
BypassESU-v5-AIO-WS2008 for Server 2008 (and Vista) - make sure to read the _ReadMe.txt - SSU KB4537830 [Feb 2020] or later is needed prior running LiveOS-Setup.cmd
I experienced an issue: installed Bypass-v5 after Feb 2020 SSU prerequisite (KB4537829), then installed 2020-02 CU, but after rebooting was stuck for over 30 minutes on "Preparing to configure windows updates". The CU eventually installed successfully however. As a test, (on another computer,) installed Bypass-v5 after Jan 2020 SSU (not Feb), and the 2020-02 CU reboot process completed very quickly (took just a few seconds) Both computers were clean, never had Bypass installed before. Question is, will there be any problems down the road, if we choose to install Bypass-v5 with Jan 2020 SSU (and not Feb SSU)?
I have a fresh install 7 back in Oct that works perfect. Notifications when updates come. The rest of the 7s I have do not give notice for updates. They all have the same Downloads from the instructions here. All windows 7s have the v5. I can manually update but rather WU let me know. I was told to refresh or reset WU. Could you tell me or post a link on this how project. Haven't had time all week to work on it till now and it was best to wait to see what or if the other 7s will do anything without manually installing it May be a quick fix. Thanks
Try to edit the LiveOS-setup.cmd and delete %%configsetroot%%\ from it at line 264: Change: Code: echo. ^<source location="%%configsetroot%%\Windows6.1-KB4528069-%xOS%.cab" /^> to Code: echo. ^<source location="Windows6.1-KB4528069-%xOS%.cab" /^> And retry the cmd.
It doesn't work with Windows Vista. I have installed all updates (except for KB4493730 because it says it doesn't apply for my system). But it just shows "ERROR" and requesting me to install these updates. I think it failed at this: reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Servicing\Codesigning\SHA2 /v SHA2-Codesigning-Support 1>nul 2>nul && set shaupd=1 if %shaupd% neq 1 goto :E_SSUSHA
Following the instructions in #1 after a Win7 clean install, + simplex, I installed the four Feb updates. Everything went smoothly and worked. Now, the computer directly starts into Safe Mode page. I can simply use the arrow to go down to Start Normally and it will do exactly that, without any further problem Where did I go wrong? Thank you (Depending on the answer, this may belong in another page?)
If one answer is enough for you, i can tell you that when you would have used UpdatePack20.3.12, it would already have all updates installed and patched WU, simplix now uses IMI-Kurwica Bypass. ps, simplix ran on a clean install will probably reboot and run in "sort of" safe mode (black background) and install updates, next it reboots and cleans up after itself.
On Friday I installed the UpdatePack7R2-20.2.12, which was the latest one at time of download, and then the Feb updates with ESU, as I did not know if they are included or not. I just now downloaded 20.3.12 and installed it, it found three uninstalled updates, and after restart, cleaning up, restart, again it offers "safe mode (black background)", but I can click downwards and it will install "Windows Normally"... What is best to do now?