L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 24, 2019 #1 I've gone through the troubleshooting steps repeatedly to no avail. I've arrived at opening the powershell step but am getting the following error. [== 4.5% ] Error: 1009 I see others with the same issue but am seeing that the fix is user specific so am starting my own thread as instructed. What is my next step?
I've gone through the troubleshooting steps repeatedly to no avail. I've arrived at opening the powershell step but am getting the following error. [== 4.5% ] Error: 1009 I see others with the same issue but am seeing that the fix is user specific so am starting my own thread as instructed. What is my next step?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 24, 2019 #3 Hello and welcome! Please follow the steps below: Step 1 - Replace Drivers Hive Manually 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 DRIVERS.ZIP and save to your desktop. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract. Now we have the DRIVERS file that we will be using to replace your current one. Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad. Note: If you get an error that the file is in use, reboot your computer and then try again. Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config Afterwards, retry DISM. Attachments DRIVERS.zip 826.3 KB · Views: 8
Hello and welcome! Please follow the steps below: Step 1 - Replace Drivers Hive Manually 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 DRIVERS.ZIP and save to your desktop. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract. Now we have the DRIVERS file that we will be using to replace your current one. Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad. Note: If you get an error that the file is in use, reboot your computer and then try again. Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config Afterwards, retry DISM.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 24, 2019 #4 Downloaded drivers.zip and extracted. Tried rebooting and renaming existing drivers file 3 times but keep getting this message.
Downloaded drivers.zip and extracted. Tried rebooting and renaming existing drivers file 3 times but keep getting this message.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 24, 2019 #5 Let me try: 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 34 bytes · Views: 3
Let me try: 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.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 24, 2019 #6 I was able to find the file that was using the driver and deleted it (Spotify). I renamed the DRIVERS file and moved the new one into the folder. After trying the DISM commands I got the same error message as before.
I was able to find the file that was using the driver and deleted it (Spotify). I renamed the DRIVERS file and moved the new one into the folder. After trying the DISM commands I got the same error message as before.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 24, 2019 #7 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.
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.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 24, 2019 #8 I gotta go to work. I'll continue this tomorrow.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 24, 2019 #11 Bingo! The hive was corrupt! Step 1 - Replace Components Hive Manually 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 COMPONENTS.ZIP and save to your desktop. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract. Now we have the COMPONENTS file that we will be using to replace your current one. Navigate to C:\Windows\System32\config Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad. Note: If you get an error that the file is in use, reboot your computer and then try again. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config COMPONENTS.zip After you replace the hive, please check whether you still have the error. Thank you.
Bingo! The hive was corrupt! Step 1 - Replace Components Hive Manually 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 COMPONENTS.ZIP and save to your desktop. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract. Now we have the COMPONENTS file that we will be using to replace your current one. Navigate to C:\Windows\System32\config Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad. Note: If you get an error that the file is in use, reboot your computer and then try again. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config COMPONENTS.zip After you replace the hive, please check whether you still have the error. Thank you.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 26, 2019 #12 I was able to run the DISM.exe command and I installed a bunch of updates but when restarting I got the "windows 10 update undoing changes made to your computer" error.
I was able to run the DISM.exe command and I installed a bunch of updates but when restarting I got the "windows 10 update undoing changes made to your computer" error.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 26, 2019 #13 Please attach CBS.log and C:\Windows\Inf\setupapi.dev.log.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 28, 2019 #14 CBS.zip Attachments setupapi.dev.log 2.1 MB · Views: 7
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 28, 2019 #15 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. Afterwards, retry updates and attach CBS.log and setupapi.dev.log if they fail. Attachments SFCFix.zip 79.6 KB · Views: 18
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. Afterwards, retry updates and attach CBS.log and setupapi.dev.log if they fail.
L LJKHBHI Member Joined Oct 24, 2019 Posts 10 Oct 28, 2019 #16 SFCFix version 3.0.2.1 by niemiro. Start time: 2019-10-28 14:18:09.322 Microsoft Windows 10 Build 17134 - amd64 Using .zip script file at C:\Users\Dan laptop\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository Successfully created directory tree \\?\C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db. Successfully copied file C:\Users\Dan laptop\AppData\Local\niemiro\Archive\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.dll to C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.dll. Successfully copied file C:\Users\Dan laptop\AppData\Local\niemiro\Archive\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.inf to C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.inf. Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2019-10-28 14:18:11.575 Script hash: A/whqs/STx16v/VzY1UoBHNv3oddwz+xLKg61w2xhxE= ----------------------EOF-----------------------
SFCFix version 3.0.2.1 by niemiro. Start time: 2019-10-28 14:18:09.322 Microsoft Windows 10 Build 17134 - amd64 Using .zip script file at C:\Users\Dan laptop\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository Successfully created directory tree \\?\C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db. Successfully copied file C:\Users\Dan laptop\AppData\Local\niemiro\Archive\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.dll to C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.dll. Successfully copied file C:\Users\Dan laptop\AppData\Local\niemiro\Archive\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.inf to C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_7d280adeda6574db\oposdrv.inf. Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2019-10-28 14:18:11.575 Script hash: A/whqs/STx16v/VzY1UoBHNv3oddwz+xLKg61w2xhxE= ----------------------EOF-----------------------
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Oct 28, 2019 #17 Thanks. Retry updates.