[SOLVED] Help with booting, DISM, and "the component store cannot be repaired"

Uninstall ASio.sys driver.

You can uninstall the third party drivers from offline Windows Operating Systems using Command Prompt within Windows Recovery Environment.
Uninstalling third party driver while Windows OS offline can be helpful in situations where Windows OS will not boot or have a Blue Screen Of Death (BSOD) because of a driver you have installed.

Dism command can only be use with following operating systems:
  • Windows 7
    [*]Windows 8
    [*]Windows 8.1
    [*]Windows 10



Boot the computer into Windows Recovery Environment and open the Command Prompt.
Display information about all drivers in an offline operating system.


Code: 
Dism /image:D:\ /Get-Drivers

uh1WzPo.png


Replace the D:\ drive letter with the assigned drive letter of the Windows OS installed partition.


Display information about an INF file installed.
Installed 3rd party drivers will be named OEM1.inf, OEM2.inf, and so on.
Use the Published Name from the /Get-Drivers list to view information on installed drivers.


Code: 
Dism /image:D:\ /Get-DriverInfo /Driver:oem1.inf

WxomQ5O.png


Replace the D:\ drive letter with the assigned drive letter of the Windows OS installed partition.
Also replace the oem1.inf driver name with driver name you want to view its details.



Removes driver package from an offline Windows operating system.

Code: 
DISM /Image:D:\ /Remove-Driver /Driver:oem1.inf

gATf12I.png


Replace the D:\ drive letter with the assigned drive letter of the Windows OS installed partition.
Also replace the oem1.inf driver name with driver name of the driver you want to uninstall.
 
Last edited:
When I try:

Dism /image:C:\ /Get-Drivers (C is the correct drive letter)

I get:

Error: 2

The driver store for the image could not be opened. Should I copy over DRIVERS registry hive from 11/29 shadowexplorer backup?

EDIT: I tried using the 11/29 shadowexplorer backup of DRIVERS registry hive. Now I am going to try and uninstall the one that seems to be giving problems. It may not be a driver though.
 
The Bcdedit | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

No don't copy Drivers registry that hive has nothing to do with device drivers.
 
AsIO.sys file is a software component of Asus PC Probe by ASUS.

You can also rename the asIO.sys file by executing below command:


Code: 
Ren C:\Windows\System32\drivers\ASio.sys  ASio.sys.bak

Replace C: with Windows 10 partition drive letter.

Reboot your computer.
 
OMG....Progress I think? OK I found and renamed the ASio.sys file.... now I am able to get to the windows login screen, of my old installation! (C drive)

BUT, the issue is.... it's the screen with the date and time on the bottom left with the blue background.

When I click, I can BRIEFLY see my user profile name and login password box, but the screen almost immediately flashes and goes back to the blue clock screen. I'm not sure what could be causing this. I did transfer over the 11/29 shadowexplorer version of DRIVERS....

Hitting keys on the keyboard doesn't work either.

What happens is the date and time start to move upwards on the screen from the bottom left when I click or type, but then they reset. It's like Windows is stuck / having trouble waking up from the sleep / hibernation screen of just the date and time
 
  • Boot your computer with Hiren’s BootCD PE.
  • Goto Start Menu -> Securiy -> Passwords -> NT Password Edit
  • Open your SAM file (It is usually located in C:\Windows\System32\config\SAM).
  • Click your username and the click ‘Change password’. To set a password, type your password both ‘New password’ and ‘Verify’ fields and then click to ‘OK’. To remove the password, leave both ‘New password’ and ‘Verify’ fields blank and then click to ‘OK’.
NTPWEdit 1
NTPWEdit 2



Download | Hiren's BootCD PE
 
That is the bootcd I have been using.

The password is not the issue. The issue is Windows not properly getting rid of the hibernation / sleep / wallpaper page with the date and time. Usually when you click or hit a key, that screen goes away and presents the login screen where you type your password and login to windows. When I type, the screen briefly TRIES to go away to show me the login but then it comes right back.

I can try to take a quick video with my phone...
 
I just now tried safe mode. I can see the mouse, it's just on a black screen though :(

UGHHH I feel like we're sooo close....this is the first time I've actually been able to see the login screen without errors and BSOD's - the key seemed to be placing the registry hives from 11/29 via shadowexplorer

Let me take a video really quick
 
That is strange we have to repair it from Safe Mode. I need you to open task manager from Safe Mode press CTRL + Shift + ESC keys and from Task Manager click File --> Run new task and type explorer.exe to launch File Explorer.

Let me know if it works.
 
when I try to launch into safe mode it just shows a black screen with the white mouse curser, no matter what I type or click, nothing happens.

But here is an update:

When I get windows into the recovery environment (not boot USB) - and then I run DISM, it NOW says "no component store corruption detected"

This is great news, it took so long to get there. Now if I could just fix this time/date screen issues.. OMG I feel like we're so close...

I feel like maybe it could be a display driver issue or something....
 
You need to execute Sfc command from Safe Mode or recovery environment. As i said before files stored within C:\Windows\WinSxS folder are not used to boot Windows OS there are backup files for Windows system files.

Also Dism command wont work from recovery environment you need to mount install.wim image file for it to repair component store corruption.


Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code: 
Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows



Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
 
I ran the sfc above and it said that it found corrupt files and successfully repaired them! This is the first time I got that to successfully work too! I did this from recovery environment, not safe mode.

Unfortunately, upon reboot, the issue remains :( :( :( :( :( :( :(
 
Is there older version of registry hives you can use to replace registry hives.

Also replace NTUSER.DAT registry hive store within user user profile folder. The C:\Users\UserName folder contains the NTUSER.DAT registry hive.
 
That's the one and only version that ShadowExplorer is able to find :(

OK let me replace that file too using the Boot CD...
 
Replaced that file, no help :(

I'm thinking maybe it's a driver issue? This is maddening.....we're so close....
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top