Win 10 - can't update, upgrade, or reset; potential driver problems too

E

ee_aa_h_oo

Member
Joined
Aug 17, 2020
Posts
7
Hello,

I'm now awfully stuck, and run out of ideas - my laptop is stuck at build 18363.657. It no longer installs any of the cumulative updates successfully (both from the update UI, and offline KB MSUs - error code 0x80070002); I believe this started right after the upgrade to 1909 in Jan, but I had been ignoring and deferring updates, having been occupied with other priorities. I was hoping that when 2004 is offered, I might be able to upgrade but to my horror that's failed too (both from the UI as well as the media creation tool/update assistant - error code 0x80070057). Windows update troubleshooter finds nothing, running the Reset Windows Update tool doesn't help. SFC, DISM finds and fixes nothing. I attempted to reset the computer, and the process terminated abruptly.

I think I may have zeroed in on the the root of the problem - I think some of my drivers are messed up. As such, printer driver won't install, and when my camera is connected via USB, photos won't transfer/the Nikon photo transfer app won't open. The DISM log is full of driver related problems, especially these guys here -

Code: 
2020-08-16 21:53:23, Error DISM DISM Driver Manager: PID=4000 TID=4028 Failed to enumerating driver packages in the driver store. - CDmiDriverStore::GetDriverPackageCollection(hr:0x80070057)
2020-08-16 21:53:23, Error DISM DISM Driver Manager: PID=4000 TID=4028 Failed to generating the collection of packages in the image. - CDriverManager::GetDriverPackageCollection(hr:0x80070057)
2020-08-16 21:53:23, Error DISM DISM Driver Manager: PID=4000 TID=4028 Failed to get the out of box driver package collection from the driver store. - CDriverManager::Internal_DoListDriverPackages(hr:0x80070057)
2020-08-16 21:53:23, Error DISM DISM Driver Manager: PID=4000 TID=4028 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:532 - CDriverManager::ExecuteCmdLine(hr:0x80070057)
2020-08-16 21:53:23, Info DISM DISM Driver Manager: PID=4000 TID=4028 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::ExecuteCmdLine
2020-08-16 21:53:23, Error DISM DISM.EXE: DriverManager processed the command line but failed. HRESULT=80070057

These same set of errors recur anytime after the upgrade and/or reset ops terminate, and just to make double sure, I keep getting these same errors when running /get-drivers on DISM both on the online as well as offline images, with the DISM session itself terminating with error 87 in CMD [i validated that the command parameters or syntax itself isn't wrong, as the process starts quite alright, and in the log runs through a bunch of drivers, and failing just before it reads ykinx64 from the driverstore].

Please, could someone help. Thanks so much in advance!

CBS Logs
 
Thank you for writing back!
Yes it is, and continuing to drive me insane. I'm this close to trying clean reinstall, but just worried if that fails too, I may lose an otherwise working computer. I've been tinkering (combination of attempted reset, repair, upgrade, update; all of which have failed) a lot since I last posted this, would you be needing the fresh CBS logs? Anything else I can provide? DISM logs for example? The latter is full of errors (apparently missing drivers, it looks like)?
 
Please do the following:

Upload Drivers Hive[/B]

  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current DRIVERS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the DRIVERS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as Dropbox or OneDrive or SendSpace and include the link with your reply.
 
Thanks.

Please start with the following:


GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
Thank you. The test is running and ETA is about 2.5 hrs. Just FYI, I ran the extended test about two weeks back, and all came out OK (no red attributes and status "Completed without error").
 
Ended up doing a clean reinstall, process got me upgraded to 2004. Looks stable. Restoring data and config back to where it was is going to be a pain, but this whole episode has taught me some important lessons. Please feel free to mark this as solved if that helps. Thanks for your time and patience.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top