J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Aug 30, 2022 #61 No dice. Attachments CBS.zip 21.5 MB · Views: 3 COMPONENTS.zip 14.9 MB · Views: 5
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Aug 30, 2022 #62 You deleted the log from the Process Monitor, so I don't have access to it. Can you please run it again, as you did before, and attach the log for me?
You deleted the log from the Process Monitor, so I don't have access to it. Can you please run it again, as you did before, and attach the log for me?
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Aug 30, 2022 #63 I see the log now in your post #55. No need to run the tool again.
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Aug 31, 2022 #64 Hi! Let's proceed with another fix. SFCFixScript.txt NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse. Attachments SFCFixScript.txt 661 KB · Views: 2
Hi! Let's proceed with another fix. SFCFixScript.txt NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse.
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Aug 31, 2022 #65 The file is quite long, so I attached the log instead. Attachments SFCFix.txt 994.8 KB · Views: 2
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Aug 31, 2022 #66 Thank you. Now, try to update again with a Process Monitor trace running. If the update fails, then provide the new CBS log, the setupapi.dev.log (C:\Windows\Inf\setupapi.dev.log) and the Process Monitor log. Instructions for how to use the Process Monitor are given in posts 42 and 44.
Thank you. Now, try to update again with a Process Monitor trace running. If the update fails, then provide the new CBS log, the setupapi.dev.log (C:\Windows\Inf\setupapi.dev.log) and the Process Monitor log. Instructions for how to use the Process Monitor are given in posts 42 and 44.
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Aug 31, 2022 #67 https://www.dropbox.com/s/usivc5txfpyvwnn/Bootlog.zip?dl=1 Attachments CBS.zip 21.5 MB · Views: 2 setupapi.dev.log 2 MB · Views: 2
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Sep 1, 2022 #68 I attach for you another fix to apply. Instructions are the same as here. Try to update after the fix. If it fails, we need a new CBS log and the C:\Windows\Inf\setupapi.dev.log Attachments SFCFixScript.txt 336.1 KB · Views: 10
I attach for you another fix to apply. Instructions are the same as here. Try to update after the fix. If it fails, we need a new CBS log and the C:\Windows\Inf\setupapi.dev.log
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,195 Location %systemroot% Sep 1, 2022 #69 @JayNDT before you run the script make sure it has v! values appended on each line, the currently attached version to DR M's has been corrected. I apologise for making the mistake.
@JayNDT before you run the script make sure it has v! values appended on each line, the currently attached version to DR M's has been corrected. I apologise for making the mistake.
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Sep 1, 2022 #70 x BlueRobot If you mean the v! before the 10.0.19041., I tested it and it exists everywhere.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,195 Location %systemroot% Sep 1, 2022 #71 If you look at the first line of my original script: Original: Rich (BB code): :: [HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_dual_1394.inf_31bf3856ad364e35_none_342cbcda1751ed79] "CT"=hex:65,00,30,00,35,00,35,00,61,00,63,00 [...] Corrected: Rich (BB code): :: [HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_dual_1394.inf_31bf3856ad364e35_none_342cbcda1751ed79\v!10.0.19041.1] "CT"=hex:65,00,30,00,35,00,35,00,61,00,63,00 [...] I didn't add the v! mark which is where the CT value belongs.
If you look at the first line of my original script: Original: Rich (BB code): :: [HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_dual_1394.inf_31bf3856ad364e35_none_342cbcda1751ed79] "CT"=hex:65,00,30,00,35,00,35,00,61,00,63,00 [...] Corrected: Rich (BB code): :: [HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_dual_1394.inf_31bf3856ad364e35_none_342cbcda1751ed79\v!10.0.19041.1] "CT"=hex:65,00,30,00,35,00,35,00,61,00,63,00 [...] I didn't add the v! mark which is where the CT value belongs.
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Sep 1, 2022 #72 It's the corrected fix I checked, and everything is in its place. Thanks for the correction. JayNDT, you can run the fix.
It's the corrected fix I checked, and everything is in its place. Thanks for the correction. JayNDT, you can run the fix.
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Sep 2, 2022 #73 I'm getting this error now, not even the option to reboot to continue the installation. "Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)" Attachments setupapi.dev.log 2.1 MB · Views: 1 CBS.zip 15.8 MB · Views: 3
I'm getting this error now, not even the option to reboot to continue the installation. "Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)"
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,195 Location %systemroot% Sep 2, 2022 #74 Could you please provide your latest COMPONENTS hive again? Ideally, I want @DR M to take a look at the issue but we're going to need the COMPONENTS hive anyway because there appears to be a few more corrupt keys. At least it seems that we've resolved the DOQ errors though.
Could you please provide your latest COMPONENTS hive again? Ideally, I want @DR M to take a look at the issue but we're going to need the COMPONENTS hive anyway because there appears to be a few more corrupt keys. At least it seems that we've resolved the DOQ errors though.
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Sep 2, 2022 #75 No worries. Attachments COMPONENTS.zip 10 MB · Views: 2
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Sep 2, 2022 #76 FYI, I'll be away this whole week, so I'll answer when I return.
DR M Sysnative Staff, Security Analyst Staff member Joined Feb 12, 2015 Posts 1,722 Sep 2, 2022 #77 Thanks for letting us know. I will have a busy week too, but I'll be around.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,195 Location %systemroot% Sep 4, 2022 #78 I'll taking over this thread for now, could you please run the attached fix script? It will address 3 out of the 4 errors identified in your latest CBS log. For the last error, could you please open a command prompt window and then the following two commands: Rich (BB code): reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865" /s reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0" /s Please post the output in your next post. Attachments SFCFixScript.txt 678 bytes · Views: 2
I'll taking over this thread for now, could you please run the attached fix script? It will address 3 out of the 4 errors identified in your latest CBS log. For the last error, could you please open a command prompt window and then the following two commands: Rich (BB code): reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865" /s reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0" /s Please post the output in your next post.
J JayNDT Well-known member Joined Jun 14, 2022 Posts 66 Sep 12, 2022 #79 CMD response below: Code: C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865" /s HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 InstallClient REG_SZ UpdateAgentLCU InstallName REG_SZ Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.mum InstallLocation REG_SZ \\?\C:\WINDOWS\CbsTemp\30978400_2776143236\Windows10.0-KB5016616-x64.cab\ CurrentState REG_DWORD 0x40 SelfUpdate REG_DWORD 0x0 Visibility REG_DWORD 0x2 InstallTimeHigh REG_DWORD 0x1d8bc9f InstallTimeLow REG_DWORD 0x104d5e68 InstallUser REG_SZ S-1-5-18 LastError REG_DWORD 0x800f0826 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865\Owners Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 REG_DWORD 0x30040 C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0" /s HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 REG_DWORD 0x0 SFC report attached. Attachments SFCFix.txt 4.2 KB · Views: 2
CMD response below: Code: C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865" /s HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 InstallClient REG_SZ UpdateAgentLCU InstallName REG_SZ Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.mum InstallLocation REG_SZ \\?\C:\WINDOWS\CbsTemp\30978400_2776143236\Windows10.0-KB5016616-x64.cab\ CurrentState REG_DWORD 0x40 SelfUpdate REG_DWORD 0x0 Visibility REG_DWORD 0x2 InstallTimeHigh REG_DWORD 0x1d8bc9f InstallTimeLow REG_DWORD 0x104d5e68 InstallUser REG_SZ S-1-5-18 LastError REG_DWORD 0x800f0826 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865\Owners Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.19041.1889 REG_DWORD 0x30040 C:\WINDOWS\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0" /s HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865 REG_DWORD 0x0 SFC report attached.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,195 Location %systemroot% Sep 12, 2022 #80 FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, please attempt to update again and then provide the CBS log(s) if it fails. Attachments fixlist.txt 264 bytes · Views: 6
FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, please attempt to update again and then provide the CBS log(s) if it fails.