Main Forum > General Computer Support

SOLVED - Win 10 MMC cannot create Snap-in

<< < (2/3) > >>

ENAR:
One more question on this: I had been using the Win10 installation DVD to access the Repair function (booting from the DVD). Your posts suggest that I boot into Windows 10 in a normal fashion, and then access the repair functionality, but where do I find it? On the DVD or from within the regularly loaded Win 10?

Thanks.

Boggin:
With Windows booted up, open Windows Explorer - click on This PC and insert the install media then double click on its drive.

When using a DVD this will start the repair install process.

If double clicking the drive takes you into the disk's files then double click on setup Application.

You'll know it has started when the Windows logo comes up.

It doesn't list it as a repair option as you get when you boot up with an install disk.

ENAR:
Almost everything worked as you described, but it simply locked on 0% with the constantly rotating circle of dots for over an hour with not change to the "progress." I may be looking at a complete re-install unless you have other ideas. I'll also try a successive Macrium restore, seeing at each increment whether the MMC functionality returns.

Thanks again.

Boggin:
You could try it again with your antivirus disabled but boot up with the install disk and on the Install screen select Repair your computer and select Command Prompt in the advanced options.

Enter bcdedit |find "osdevice" and using whichever partition letter, enter and use that instead of the X I've used in this cmd -

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

That may sort out the MMC if that is the cause of the repair install sticking.

That is a Pipe symbol before find and is the uppercase of \ and note the space before each /

You need to do the bcdedit cmd because it doesn't always see the volume as being in C: in that mode.

ENAR:
OK. This is what I found:

The command 'bcdedit|find "osdevice"' found nothing. This is a dual boot drive (Win 7 and Win 10, with another partition once intended for Ubuntu (but not currently used).

To simplify things, I created empty folders in the root directories of each of the OS's labeling them: "1 - This is Win 7", and on the other "1 - This is Win 10". Using the number one ahead of the description tended to list these empty directories toward the top of the list for that drive.

With that done, and booting to the command prompt from the Win 10 DVD, I ran the sfc /scannow /offbootdir=d:\ /offwindir=d:\Windows where the d: drive was, indeed, the Win 10 drive.

After a while, it produced this response:

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.

When I looked at that log, it listed a LOT of items that were not fixed.

Correct me if I am wrong, but it is seeming more prudent to wipe the partition, and reload Windows 10 - and bite the bullet about re-installing all of the apps currently loaded.

Any thoughts? Again, my thanks for your assistance.

Navigation

[0] Message Index

[#] Next page

[*] Previous page