B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 4, 2019 #21 Still error 0x80073701, logs attached and uploaded. I hope we don't have to keep on doing this for each of the 50 corrupted manifests reported in the first place Attachments CBS.zip 5.9 MB · Views: 2 Fixlog.txt 3.4 KB · Views: 3
Still error 0x80073701, logs attached and uploaded. I hope we don't have to keep on doing this for each of the 50 corrupted manifests reported in the first place
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 4, 2019 #22 Which language packs have been installed onto the system?
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 4, 2019 #23 German (Germany) only
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 4, 2019 #24 Do you happen to have another machine running Win10 1903 German available? I'm looking for a specific registry key.
Do you happen to have another machine running Win10 1903 German available? I'm looking for a specific registry key.
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 5, 2019 #25 Yes I do, which key is it?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 5, 2019 #26 Can you please upload the COMPONENTS hive from that other machine?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 5, 2019 #28 Thanks. Attachments fixlist.txt 2.9 KB · Views: 6
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 5, 2019 #29 And another 0x80073701 error, logs attached and uploaded. Attachments CBS.zip 3 MB · Views: 0 Fixlog.txt 3.6 KB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 5, 2019 #30 There was a small error in my previous fix. Please do the following. Attachments fixlist.txt 2.9 KB · Views: 3
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 5, 2019 #31 After applying your last fix, I'm getting a 0x80073712 error now. Logs attached and uploaded. Attachments Fixlog.txt 3.6 KB · Views: 1 CBS.zip 2.9 MB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 5, 2019 #32 Please look for the following file on the other machine: C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.1_de-de_86fefe8a424eee46.manifest
Please look for the following file on the other machine: C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.1_de-de_86fefe8a424eee46.manifest
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 6, 2019 #33 There it is Attachments manifest.zip 1.2 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 6, 2019 #34 SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text. Attachments SFCFix.zip 1.6 KB · Views: 3
SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 6, 2019 #35 Another 0x800f081f error, logs attached and uploaded. Attachments Fixlog.txt 3.6 KB · Views: 0 CBS.zip 3 MB · Views: 2
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 6, 2019 #36 Did you run SFCFix as I told you to?
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 6, 2019 #37 Yes I did, I uploaded the wrong log, here it is. Attachments SFCFix.txt 2.1 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 6, 2019 #38 Step#1 - 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. Attachments fixlist.txt 353 bytes · Views: 6
Step#1 - 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.
B brinox Well-known member Joined Oct 3, 2019 Posts 138 Location Germany Oct 6, 2019 #39 Done. Now I'm getting the 0x80073701 error again. Logs attached and uploaded. Attachments Fixlog.txt 1,012 bytes · Views: 1 CBS.zip 2.9 MB · Views: 0
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 6, 2019 #40 Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.