WINDOWS 10 USB NOT WORKING DISM CORRUPT

D

Decrypt

New member
Joined
Jun 17, 2016
Posts
4
About two weeks ago i woke up to my pc not recognizing my usb devices

So i began updating the drivers manually from Device manager and the harddrives for some reason accepted the generic volume drivers and worked,

Other devices as seen below never work, path cannot be found errors. I found registry database corrupt when trying to update the intel ME.

DEVMAN.jpg - Google Drive


Looked this up to find that the corrupt database error is an on going issue.

So i ran sfc /scannow and it picked up no errors
I ran DISM command to repair image and get the error component store corrupted 14098

I downloaded a new iso image with the same build as mine from techbench and ran the dism command using the install.wim file from the new iso which i copied to another directory (not read only)

still get the same annoying message,

So i tried to do an INPLACE upgrade, after accepting T&C and keep settings screen on the install screen my cursor displays a loading circle and then setup fails

Ive tried almost all online options that i could find and no success at all,

Google Drive: DISM LOG from SFCFix as well as my setuperror log from panther directory after trying INPLACE UPGRADE as well as DRIVER file from component store

dism.zip - Google Drive
DRIVERS.zip - Google Drive
setuperr.zip - Google Drive

PLEASE GUYS HELP, i dont want to do a clean install and lose programs:noidea:DEVMAN.jpg
 
Hi Decrypt ... and welcome to the forums ...

Sorry that we've been a bit busy...... I'll hope to have some time to look at your files very late Friday or on Saturday. (of course, another tech might drop by sooner)

In the meantime - if you haven't run full diagnostics yet, give them a go. Any built-in diagnostics can be especially handy, as they also test I/O to and from critical motherboard modules. Run the diagnostics on as thorough settings as you can, for the best results. If there are no built-in diagnostics, at the very least make sure to test the memory and hard drive. The latest version of MemTest86 has been updated to work with the newer DDR4 modules and the latest chipsets. Diagnostics from the manufacturer of your hard drives work the best.

Also, check your Bios settings. Have a look at the temps in there, too (should be very good while in the Bios, since little is running). If anything is overclocked, dial back to defaults. Of course you'll want to double-check the few USB settings in there (Legacy USB is usually best enabled for easy compatibility with mice & keyboards). Memory timings, hard drive settings... check all "the usual suspects".

As General MacArthur once said (long before the Terminator movies) "I'll be back" .....
 
Ill do some diagnostics on hardware,

however i forgot to mention that i am running two seperate windows 10 OS. One for CG and the other strictly gaming.

The secondary OS which i use for gaming doesnt report any issues or corruption at all and everything works perfectly on that system.
 
Hi again


Do you hide the two systems from each other?

The few techs that I know have tried to have two of the same versions of Windows on one PC did it by installing each one separately, on separate hard drives (not just separate partitions). They actually choose which drive to boot from at startup (using the BIOS/UEFI boot menu). I've dual booted various versions of Windows on my computers in the past, but usually not two installations of the same version of windows on the same computer. Even with different versions, odd problems show up (remember how having a dual boot Vista/XP computer would kill off System Restore?)....

I've never had any issues with multi-booting when I install Linux as the last operating system. When Linux is the last installed, the boot menu can then be the more multi-boot tolerant Linux bootloader (Grub, Grub2, or any of the other variants).

Since your gaming installation of Windows 10 is completely stable (on the same hardware?) ... I'd guess that it is the installation handling the boot menu? Or?

There are some bootloader programs that can boot darn near any combination of operating systems ... but I haven't been actively multibooting much other than simple Windows/Linux combos lately. I'm not sure how Windows 10 - with all its changes - handles multiboots.

If the CG installation is on a separate physical hard drive (which I'm guessing is likely) -- have you tested the drive to make sure that it is functioning OK?

I have to wonder if the DISM errors in your logs are the result of DISM trying to figure out which Windows system folder is it's target. Pretty odd looking errors... I don't often have to worry about DISM logs, as the process basically either works to restore a healthy image, or it doesn't. The fact that the CG system can't find the driver store is odd ... those aren't rare devices, Windows 10 has drivers for all of them.

I wonder what would happen if you try the in-place repair of the CG system again (but with the gaming system's hard drive disconnected ... if it is a separate physical hard drive.... or with the gaming system's partition hidden). Then, if that fixes the CG system, on another drive or partiton (if you have room) try a small installation of Linux, with both Windows drives/partitions connected ... but only boot from a Linux Live DVD to initiate the Linux installation. Linux should find and create a boot menu for both Windows 10 installations, and for itself. And hopefully the two Windows systems won't get confused by each other (although they might... it seems they already did once).

I'm going to have to look up the latest details on multibooting -- because unless there is a physical or configuration problem with the CG system's disk/partition -- I'm thinking that it isn't too far-fetched to think that some of Windows 10's disk management features, especially the Shadow-copy services, defragmentation services, and such -- are having a bad effect on the CG system's setup.

Or perhaps an update happened for the CG system that went haywire.
_________________________

One quick-fix try you can do .... on the CG system, see if you have a System Restore point from before things went sideways. If you do, try a System Restore for the CG system (might be best if the gaming drive/partition is disconnected/hidden during the restore).

I'll have a look around at the latest details for Windows 10 multiboots. If you are using a specialized bootloader, let us know which one.

I think that's going to require at least three cups of coffee!
 
So i managed to run some diagnostics.

Memtest reported no issues with RAM,

My CG install is running of a solid state drive, ive ran diagnostics from the manufacturer with no problems reported.

My GAMING OS runs on a traditional hdd which also reports no errors.

My gaming OS is as you said the main boot device from where the bootloader runs.

Ive hidden the Gaming OS by disabling the harddrive completely and still have the same errors on DISM and when i run the INPLACE Upgrade from within the CG menu

I picked up something strange though, when i boot using a bootable win10 usb with the latest build, and run sfc through the cmd repair screen it keeps telling me a sfc operation is pending reboot and when i reboot it keeps saying the same thing so i cannot run sfc through that screen.

Legacy usb compatibility is enabled in the bios/uefi menu

My Gaming build has not been updated whatsoever since my initial install. My CG install is the latest build which i had to update to for some program/s requirements.

No system restore as i always have it disabled :banghead:

Im really out of clues as to why its so messed up
 
Hi again


Sorry that this is taking a while ....

I'm having trouble finding a reliable source for the exact details for a two-installation system, where both installations are Windows 10, on the same motherboard, using the same bootloader. As I mentioned, I've created and used many multi-boot systems in the past, but never with two of the same Windows version. This is partly because Windows tends to think it should be top dog in any environment, and tends to want to mess with the configuration of any hardware that it sees (which in your case would be the other hard drive with the other installation of Windows 10 on it). Also, Windows licensing is complicated enough without having two licenses linked to one motherboard. So - I've always kept the current version Windows on separate physical machines [if I had a supercomputer, however, I might dally with virtual machines].....

I've just now started looking at your error logs .... (busy weekend with Father's Day and all) .... and so far, the setup error logs and the start of the DISM errors (I'm not quite 25% through) ... are pointing to things like suspected file corruption, or simply not being able to either find or access certain files and locations.

I'll have to really get a good look at your situation, since it's something I haven't seen before. Might take a bit longer than average.

One thing that I wasn't sure what you meant: when you were updating drivers just after the USB issues showed up, you mention something about your hard drives showing up as "Generic Volumes". That doesn't sound right - I usually see "generic volumes" when Windows is referring to USB external drives & such. Did you see the hard drives listed as "Generic Volumes" in Device Manager, instead of seeing the Manufacturer & model number? If not, that's a problem - it means Windows can't get to the place it stores a record of your devices.

Let me do a little more research, and finish looking through the error logs - and I'll check back again.
 
Quick Hello today....

I haven't had much luck finding any reliable information on dual-booting a system with two versions of Windows 10 (without using a "virtual machine").

I think my recommendation would be to simply go with one installation of Windows 10.

It would simplify things. No need to try to hide drives or partitions. And your antivirus protectors have fewer files to scan (might speed up any scheduled scans).

Thoughts?
 
Hey Gary

The generic volume issue was specifically with USB plugged in hdds. however after i installed them as generic they worked fine and to date they have not troubled at all. The few devices that remain with exclamation marks next to them in the devman say registry database corrupt and fail to install whether from online, or local driver. I really will love to keep both OS as they worked out excellent.

Any idea why sfc will say it has a pending reboot operation everytime i ran it from repair screen? and when ran from the OS booted it gives me operation could not be completed.

I dont know if there is anyway to fix these issues at all.
 
Hi again

I haven't ever seen that particular "pending" error before for sfc, but I looked around, and evidently quite a few folks have run into the same problem. A helpful tech was nice enough to provide us with a DISM command that can help clear up the error. Here is that guide:
[FIX] There Is System Repair Pending Which Requires Reboot To Complete

I think what you could try next (if your Internet is stable enough on the affected OS) is to use that same DISM tool, but this time using a different command:


Running DISM online


1) Right-click the Windows Start Menu icon
2) From the menu, select Command Prompt (Admin)
3) To the question "Do you want to allow this app to make changes to your computer?", select Yes
7) Type in the following command: Dism /Online /Cleanup-Image /RestoreHealth


This can take quite a while - it varies a lot from machine to machine, and the speed of the Internet connection can add extra time when slow. Even if the "Percentage Complete" stops for a long time at a certain percentage, wait it out: it's fairly normal for the percentage displayed to not get refreshed for quite a long time.
_________________________

If the DISM system health restore finishes successfully (it will say so if it does), you can then try another run of the SFC tool if you'd like. If it finishes without errors, then things should be looking up.

To be extra-thorough, you also might want to try forcing a CheckDisk on the hard drive holding the troubled Windows 10 installation ... just to make sure that the NTFS file system is ship shape. You can schedule that from within an elevated Command Prompt, using the chkdsk /r command, then allowing it to run on reboot.
____________________

I still think that only having one Windows 10 installation on the computer would be more efficient & less prone to strange behavior that might send you on regular visits to our forums :)

Good for comedy though, yes? .... (my kids tell me I'm as goofy as I am grumpy, and I tell them it's one of the privileges of old age)
 

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

Back
Top