View Single Post
  #2  
Old February 22nd 17, 09:47 AM posted to alt.comp.hardware.pc-homebuilt,alt.comp.os.windows-10,alt.comp.os.windows-8,alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Restoring MIcrosoft Basic Display Adapter

Mr. Man-wai Chang wrote:

I deleted the Microsoft Basic Display Adapter and its drivers by mistake
while doing a hardware upgrade.

Is there an easy way to restore them?

Reinstalling the OS would surely fix the problem... but would like to do
that later when all else fail.


Do you have System Protection enabled on C: ?
Is there a System Restore point from before the mistake happened ?

A second possibility, is open Device Manager and see if there
is an option to "roll back" the driver. Driver roll back is
one level deep. You can put back the previous driver, before
you made a change.

That's all that comes to mind, short of using a backup
you made of the OS C: partition at some point. For example,
I made one backup of C: already, before doing some experiments,
so I occasionally have something sitting there which can be used.

*******

When you delete files in System32, they also exist in WinSXS. The
OS hard-links files from WinSXS into System32. When you delete
a file from System32, it isn't really gone. All you've done is
erase the 1KB $MFT entry, not the actual clusters.

The OS has two levels of repair. This one should repair
System32, using resources from the driver cache or from WinSXS.
This puts info into a .log file as well, as to what was repaired.
You can run this from an Administrator Command Prompt (available in
the right-click of Start Menu, unless you're using the Insider Edition).

sfc /scannow

The other kind of repair, is to WinSXS. It's done using
DISM and a network connection to the Microsoft server.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
corruption marker is already present in the registry.
It is just a quick way to see if corruption currently
exists, and to inform you if there is corruption. It
does not fix anything or create a log.
This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
It only checks for component store corruption and records
that corruption to the log file.

This is useful for only logging what, if any, corruption
exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
records the corruption to the log file, and FIXES the
image corruption using Windows Update. This should take
around 10-15 minutes up to a few hours to finish depending
on the level of corruption.

Paul
Ads