New
#61
Choose 'Windows 10'
BSOD ERROR - Critical_Process_Died
-
-
-
New #63
My usb drive when I plug it in, instead of coming up as Local Disc, it came up as MULTIBOOT. Do you know anything about that? I couldn't find anything on google. and after placing the ISO on it, image health isn't recognizing the drive.
-
New #64
I believe that extracting such ISO's rename the USB device, it happened sometimes to me.
Enter 1 of below commands, %setupdrv% is the directory to the file (correct it to the directory path)
Code:Dism /Online /Cleanup-Image /RestoreHealth /source:wim:%setupdrv%:\sources\install.wim:1 /limitaccess Dism /Online /Cleanup-Image /RestoreHealth /source:esd:%setupdrv%:\sources\install.esd:1 /limitaccess
-
New #65
Is there anyway to rename the drive back to normal, and make it function normally again? I tried renaming in properties but it made the name all caps no matter what and it didn't seem to change anything.
-
New #66
The way you do it is the easiest way, a reboot could help.
Format it.make it function normally again?
-
New #67
I already tried a quick format multiple times and that didn't do anything as far as the name issue goes and image health still didn't recognize it.
-
New #68
A format doesn't do anything about the name, only the data...
Run an admin command prompt and copy/paste the command I posted earlier with a small edit.and image health still didn't recognize it.
-
-
New #69
Ok, I'll use one of the commands, but what I meant with the previous post was, if ImageHealth still isn't recognizing the drive I can only assume that the same behavior would be exhibited by other programs I use in the future that require me to use a USB for whatever reason. Is there a way to fix my usb so that I can use it in the future?
-
Quote
Related Discussions
