-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INACCESSIBLE_BOOT_DEVICE BSOD #185
Comments
Okay so now I feel a bit stupid. I haven't thought about the possibility that Windows RE might now have the RAID drivers I need. After adding them to the WinRE image I managed to use the previously mentioned restore point. |
hm... noted as bug |
@FluidExtractor can you name what is the name of .sys file of AMD RAID Drivers which you have? and what version if that is STOREMI or not? |
@ionuttbara rcraid.sys rccfg.sys rcbottom.sys |
does not matter. i just want to know its STOREMI or not. working on fix. sorry for late response, i just switching the remover to powershell version, and made some fixes. |
What does the bug affect?
The ability to boot into Windows
When does this occur?
After running the script with the "Remove Windows Defender Antivirus + Disable All Security Mitigations" option on a system with software RAID set up I can't get it to boot.
In which version of Windows does this issue happen ? Write version complete.
Windows 11 22H2
How do we replicate the issue?
Expected behavior (if you have any solution write here.)
Other Comments
I made a restore point prior to running the script but it's useless since Windows RE doesn't detect the Windows install.
The drives themselves are fine, since I can access them without problems after booting a separate Windows install from an external drive and installing AMD's RAID drivers. Considering that I can access the drives, I could try reverting the changes made by the script. Although knowing which part of the script messed things up would be helpful.
Any help/ideas would be appreciated.
The text was updated successfully, but these errors were encountered: