The timestamp in the update log points to the error: Code: %windir%\WindowsUpdate.log 2021-08-11 21:35:18:006 4500 119c Handler FATAL: CBS called Error with 0x8007371b, More info in the CBS.log: Code: %windir%\Logs\CBS\CBS.log 2021-08-11 21:35:15, Info CSI 000001a9 Changelist winner missing its manifest - d458e40dc4155d5c1e7758c5083b42aa, Version = 11.2.9600.20044, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral 2021-08-11 21:35:15, Info CSI 000001aa Changelist winner missing its manifest - 04fc816fc670453a5d0a95e87462bd37, Version = 6.1.7601.24565, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral 2021-08-11 21:35:15, Error CSI 000001ab@2021/8/11:19:35:15.247 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(935): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null) This is what reg knows about the two guids: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_d458e40dc4155d5c1e7758c5083b42aa_31bf3856ad364e35_none_ad348494c685be5d] @="11.2" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_d458e40dc4155d5c1e7758c5083b42aa_31bf3856ad364e35_none_ad348494c685be5d\11.2] "11.2.9600.20044"=hex:01 @="11.2.9600.20063" Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_04fc816fc670453a5d0a95e87462bd37_31bf3856ad364e35_none_cf2865108824a4ee] @="11.2" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_04fc816fc670453a5d0a95e87462bd37_31bf3856ad364e35_none_cf2865108824a4ee\11.2] "6.1.7601.24565"=hex:01 @="11.2.9600.20063" both manifest files are July 2021: Code: %windir%\winsxs\Manifests\amd64_d458e40dc4155d5c1e7758c5083b42aa_31bf3856ad364e35_11.2.9600.20063_none_90bd35037ccadae9 <?xml version="1.0" encoding="utf-8"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0"> <assemblyIdentity name="d458e40dc4155d5c1e7758c5083b42aa" version="11.2.9600.20063" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <deployment /> <dependency discoverable="false"> <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-Scripting-JScript9.Resources" version="11.2.9600.20063" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> <dependency discoverable="false"> <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-Scripting-JScript9.Resources" version="11.2.9600.20063" processorArchitecture="x86" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> </assembly> Code: %windir%\winsxs\Manifests\amd64_04fc816fc670453a5d0a95e87462bd37_31bf3856ad364e35_11.2.9600.20063_none_e2681dcbae34bfd0 <?xml version="1.0" encoding="utf-8"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0"> <assemblyIdentity name="04fc816fc670453a5d0a95e87462bd37" version="11.2.9600.20063" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <deployment /> <dependency discoverable="false"> <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-IE-JavaScriptCollectionAgent" version="11.2.9600.20063" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> <dependency discoverable="false"> <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-IE-JavaScriptCollectionAgent" version="11.2.9600.20063" processorArchitecture="x86" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> </assembly> obviously reg points to wrong file versions, fixed reg: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_d458e40dc4155d5c1e7758c5083b42aa_31bf3856ad364e35_none_ad348494c685be5d] @="11.2" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_d458e40dc4155d5c1e7758c5083b42aa_31bf3856ad364e35_none_ad348494c685be5d\11.2] @="11.2.9600.20063" "11.2.9600.20063"=hex:01 Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_04fc816fc670453a5d0a95e87462bd37_31bf3856ad364e35_none_cf2865108824a4ee] @="11.2" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_04fc816fc670453a5d0a95e87462bd37_31bf3856ad364e35_none_cf2865108824a4ee\11.2] @="11.2.9600.20063" "11.2.9600.20063"=hex:01 And KB5005088 finally installs without error. Seems like July Rollup messed that up. Edit Sept 21: Another similar July registry problem lurking apparently, failing September 2021 Rollup with code 8007371B again. Code: %windir%\Logs\CBS\CBS.log 2021-09-16 15:26:35, Info CSI 000006bc Changelist winner missing its manifest - 7148c4b88270109b439d08751ada33e5, Version = 11.2.9600.20044, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Another manifest file from July 2021: Code: %windir%\winsxs\Manifests\amd64_7148c4b88270109b439d08751ada33e5_31bf3856ad364e35_6.1.7601.25653_none_e6026885e3e85bb4.manifest <?xml version="1.0" encoding="utf-8"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0"> <assemblyIdentity name="7148c4b88270109b439d08751ada33e5" version="6.1.7601.25653" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <deployment /> <dependency discoverable="false"> <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-LUA" version="6.1.7601.25653" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> </assembly> this time reg contains an additional version entry: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7148c4b88270109b439d08751ada33e5_31bf3856ad364e35_none_91ebf6a32cfce568] @="6.1" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7148c4b88270109b439d08751ada33e5_31bf3856ad364e35_none_91ebf6a32cfce568\6.1] "11.2.9600.20044"=hex:01 @="6.1.7601.25653" "6.1.7601.25653"=hex:01 Fix is to delete "11.2.9600.20044"=hex:01 key: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7148c4b88270109b439d08751ada33e5_31bf3856ad364e35_none_91ebf6a32cfce568] @="6.1" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7148c4b88270109b439d08751ada33e5_31bf3856ad364e35_none_91ebf6a32cfce568\6.1] @="6.1.7601.25653" "6.1.7601.25653"=hex:01
I'm unclear on something, starting with a clean installation should all servicing stack updates be installed or only the latest? Latest is currently July 2021 Servicing Stack Update for Windows 7 for x64-based Systems (KB5004378), is that all that's needed? Thank you
Moin T1925redtr! Before using BypassESU v9 or v11 after an clean installation, the following updates should be applied: KB3138612: Windows Update-Client KB4474419: Update SHA-2-Code-Signing Version 3 KB4490628: Servicing Stack Update KB5004378: Latest Extended Servicing Stack Update More information can be found in the _ReadMe text file of the BypassESU package. Please read! abbodi1406 has taken a lot of trouble to explain all this in detail.
Try right-clicking on the link and click "save link as". That should open up the window. If you're using Chrome you'll also have to click "Keep" if it comes up with a malware warning. Always happens to me on the MS update catalog. Also if you're using any privacy extensions like uBlock, AdBlock or Ghostery, try whilelisting the update catalog site in those, as they seem to block downloads from there.
I had similar problems with the update catalog, with chrome, firefox and internet explorer, I only managed to download using edge browser
Unfortunately, I am getting Error 66A while trying to install KB5004871 (2021-08 .NET) although KB5005088 (2021-08 Rollup) installed fine. Please tell me how should I resolve the issue. Thanks in advance. Edited: After replacing a missing installer file, the update installed fine. Thanks to the Bypass Team again. It is due to the hard work and dedication of yours that we are getting updates smoothly.
Hello everyone, I'm using this fantastic tool for a long time. After a Windows update some time ago, Acrobat Reader stopped working with error “Acrobat Failed to Load core DLL” I temporarily uninstall BypassESU completely and this solved the issue, then I found this notice I forgot: - Important Notice about the .NET 4 ESU Bypass it has incompatibility issue and may cause msiexec.exe or other programs to stop working therefore, it's recommended to install it only when new .NET 4 updates are available, then remove it after installing the update I know it's already written in the first post, but probably repeat could help others Regards, Pyornkrachzark
Thanks for answering, I do always read all documentation, I just wasn't 100% clear on whether servicing stack updates were cumulative and was trying to get clarification. I understand now that you can simply install only the latest with the prerequisite that the SHA-2 code signing updates are installed.
TrueImage.exe (Acronis true Image backup) not starting on 32bit error: Faulting application path: D:\Program Files\Acronis\TrueImageHome\TrueImage.exe Faulting module path: D:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCR80.dll The ms c++ runtime dll is not executing correctly allthough the dll loaded fine... Removing the .NET 4 ESU Bypass solves the problem. maybe this can help others facing same problem !
Sorry for the late reply. Actually, I shifted all my Windows Installer files from C drive to another drive in order to save space in C Drive. When I got the above error, I just copy pasted all the Installer files back to C drive. That solved the problem.
Sorry for the late reply. Actually, I shifted all my Windows Installer files from C drive to another drive in order to save space in C Drive. When I got the above error, I just copy pasted all the Installer files back to C drive. That solved the problem.
Yes, this is easy right - just see list of installed updates, if you have installed newer then latest non ESU.
Do i need do this procedure just one time and I'm in ? Or i need update this frequently to keep getting security updates?
One time for Bypass ESU but if any update to Bypass ESU is published then need to see whats updated & if theres a need to run updated tool or not according to our needs. Mostly it's updated for .net .
Hello, after a full installation of BypassESU-v11 (option 1 of the menu) when I tried to remove WU ESU Patcher (option 4 of the menu) this error is returned in the output: ... removing "C:\Windows\WuEsu\" removing "C:\Windows\System32\wuaueng3.dll" 'removing' is not recognized as an internal or external command,operable program or batch file. removing schedule task "Patch WU ESU" ... I think in line 320 of file LiveOS-Setup.cmd there is a missing echo command, so this line should be if exist "%SysPath%\sle.dll" (echo removing "%SystemRoot%\System32\sle.dll"&del /f /q "%SysPath%\sle.dll") Could you please double check and if you agree update the cmd file? Thanks, Pyornkrachzark
thank you for your time and offer the tool working perfectly ... i am waiting for the next monthly rollup 9-2021