View Single Post
  #11  
Old October 26th 17, 11:03 AM posted to alt.comp.os.windows-8
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Asus X550J laptop

Paul wrote:
Mayayana wrote:
"Paul" wrote

.... Secure boot seems to be at least part of the problem.
With that turned off I'm getting either a login to reset
or error c000021a. Ophcrack can't find a password
needed for the reset. But it's progress. Thanks. I never
would have thought of secure boot acting like the hard
disk is loose!


I had a chance to try the dism and sfc commands.
While booted from the DVD and using the Command
Prompt window.

My first problem was, I had older media downloaded
from the MicrosoftStore. It uses install.esd instead
of install.wim. I tried to get dism to mount the .esd
and it refused.

So I ended up downloading fresh media, using the
Heidoc URL generator to generate links. That got
me some media with install.wim as the largest
file on the image.

If you mount the ISO file on your technician machine,
or if you use 7ZIP, you can copy the install.wim from
the \sources folder. The install.wim has multiple OSes
stored in it, indexed by an "index" number. Here, I'm checking
the first index of the WIM, to see if it's a copy of Pro.
This particular WIM has two OSes in it, Pro and Home,
and there is no "/index:3".

dism /get-wiminfo /wimfile:f:\install.wim /index:1

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Details for image : f:\install.wim

Index : 1
Name : Windows 8.1 Pro
Description : Windows 8.1 Pro --- the one I need
...
The operation completed successfully.

I copied that install.wim file, to the root of C: on
my simulated "broken" drive. I did that so I would
be sure to be able to access it.

Next, was the actual dism run to repair the content.
The command syntax was slightly different, as booting
from the DVD is not the same as the example I found.

In my simulated environment, the C: drive becomes D:
when you boot to Command Prompt to do repair work. That's
why the following might be a bit difficult to understand
without a guide. It takes some time for the WIM to be
unpacked.

mkdir d:\mount

dism /mount-Image /ImageFile:d:\install.wim /index:1 /mountdir:d:\mount\ /readonly

Now, time to actually run a dism command. The d:\mount\windows
contains the "golden" set of files. And d: is the thing being
repaired.

dism /image:d:\ /cleanup-image /restorehealth /source:d:\mount\windows /limitaccess

Deployment Image Servicing and Management tool
Version: 6.3.9600.16384

Image Version: 6.3.9600.16384

The scratch directory size might be insufficient to perform this operation.
This can cause unexpected behavior.
Use the /ScratchDir option to point to a folder with sufficient scratch
space. The recommended size is at least 1024 MB.

[==========================100.0%================== ========]
The restore operation completed successfully.
The component store corruption was repaired.
The operation completed successfully.

Then I could try an SFC to finish the job.

sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

Beginning system scan. This process will take some time.
Windows Resource Protection did not find any integrity violations.

In principle, I could then boot into the OS on the
hard drive, as all of its corrupted system files at
least, would be put back. You could still have registry
damage, home directory damage, a ton of other stuff.

That's it,
Paul
Ads