New
#640
Everyone of the ISOs I have only show win 10 home using the call cmd. This is really annoying.
Not sure how you obtained the ISO files, but Microsoft uses a utility called Media Creation Tool to download and create an ISO file or a bootable USB stick. That process results in a multi-Edition ISO for Windows 10.
However, even if you only have Windows 10 Home edition in your WIM file, you can use that to create a Pro Edition image for repair purposes. Basically, DISM can "Apply" the install.wim to a folder, which is like unzipping all of the files it contains. Then a DISM command will convert it to a Pro image.
It seems like it should be much easier to download a mult-edition ISO from Microsoft, but here is how to create a Pro image from a Home edition WIM file. I will use H: for the drive letter of the ISO and C:\PRO\ for where the Windows image will be placed. You need to create the C:\PRO folder first, or whatever folder you want to work with.
This will copy an entire Windows 10 image, from Index:1 of a WIM file to C:\PRO\.Code:DISM /Apply-Image /ImageFile:H:\Sources\install.wim /Index:1 /ApplyDir:C:\PRO /CheckIntegrity /Verify
To confirm the Edition:
To change the Edition from Home to Pro:Code:DISM /Image:C:\PRO\ /Get-CurrentEdition
If you began with a Home image at C:\PRO, you will now have a Pro Edition image there. You can now use this as a repair source instead of the WIM file.Code:DISM /Image:C:\PRO\ /Set-Edition:professional
Code:DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\PRO\Windows\
Your issue is different than the topic of this thread. You can use DISM to repair Windows, even if you only can boot to the Command Prompt, as you say, but your Windows folder may be OK, even if it says "inaccessible boot device". So you may not even require DISM repair on your Windows. You can check it using sfc.However, in Repair mode Windows might not be on C:. It could be on D: or another letter, so the command would need to be adjusted.Code:sfc /SCANNOW /OFFBOOTDIR=C:\ OFFWINDIR=C:\Windows
The System partition is separate from the Windows/Boot partition. The System partition can be entirely deleted and rebuilt without changing the files at C:\Windows. It is easier on a UEFI BIOS-mode device, because the winre.wim file (which is what you are booting to when your normal boot fails) is on a separate partition for UEFI. In Legacy BIOS mode, winre.wim is on the System partition, so has to be moved elsewhere if you want to recreate the System partition.
Everything worked except last line; DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\PRO\Windows\ error 2 system cannot find file specified.
adm2019,
Save all of the important files to another drive or to the cloud.
See if you can make a Kyhi boot rescue flash drive:
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
If there are problems downloading the tool then you can use Ubuntu:
Create a bootable USB stick on Windows | Ubuntu tutorials
Linux to the rescue! How Ubuntu can help a computer in distress | PCWorld
Using Kyhi boot rescue test the drive using HD Tune: (free version)
https://www.hdtune.com/
Using Ubuntu test the drive using HD Sentinel for Linux: (free version)
Hard Disk Sentinel - Free Linux version
Use a camera or smartphone camera as needed.
Save images for all test results.
Ten Forums has a forum for BSOD.
You can open a new thread in the forum.
If troubleshooting steps cannot fix the underlying problem you can plan to perform one of the following steps:
a) custom install (saves files, reinstall applications and drivers)
if the above fails then:
b) clean install (deletes files, reinstall applications and drivers)
OK printer is now repaired by deleting drivers in registry, so that fixes my main concern but now I have 3 folders under C drive that were not there before trying to repair and all have at least 3gb of files in them. Windows~BT, ESD, Pro and Windows 10 Upgrade plus a couple others that can be deleted easily. Still DISM won't run to finish.
You should be able to use even a running copy of Windows, somewhere on your network, if the Windows folder from that computer was shared.
Maybe my syntax is wrong, and it does not like the last slash \. The DISM errors are not very clear as to exactly what is wrong. Sometimes you can sort it out in the logs that get created, but they are huge to look through.
For some reason, if I recall right, you were getting this Error 2, even if you do not point to a Source?
This particular drive has not crashed yet just errors that prevented printer from working is why I was trying to fix it with DISM and then reinstalling/repair (which none worked) but the pc itself is ok for now. I use a removable rack and all my BSODs happened on my enterprise editions and I know I have a hardware failure according to their event viewers. Since this one is working for the most part then I guess there problem could be their ssds failing. Gonna let this one ride as long as it will work while I complete building my new rig, thanks for all the help.