Correction. There *must* be a space between bcdedit and the forward slash. There is no command called "bcdedit/set" (for good reason)

Good information and thank you - it worked nicely. :)

this works, thanks

I used the ALT commands

This approach worked on my Windows 10 machine - which should have been set up with AHCI in the first place since all of my drives are SSD. However one must know that it may take several reboots for your D: disk to re-appear and become stable. In the first reboot, my data appeared to have been lost. After swearing at the computer several times, I decided that perhaps a reboot would help the situation. Fortunately after 2 more reboots, the disk re-appeared and all of the data was intact.
Thank you for these steps to switch my computer from RAID to AHCI.

Added a Samsung 970 Evo (500GB) NVMe M.2 alongside the existing HDD in new Dell Inspiron 5570. Samsung software couldn't load the drivers because drives configured for RAID. I set AHCI in BIOS and W10 (home) wouldn't boot up. Returned to BIOS to RAID and rebooted successfully. Found this thread and tried it. Yes, it worked! It took a bit of work to manipulate the the drive letters afterwards but got there eventually. Thank you for the information.

I had a really odd experience attempting this on Windows 10, but I finally figured it out:
When I switched to AHCI and got to the safeboot menu, my keyboard wouldn't work. If I tried to get to the keyboard settings nothing happened. I was able to get to the Command Prompt terminal via the 'Windows Systems' tab in the Start Menu. Once I had opened the Command Prompt, I could type in it using the on-screen keboard (Start Menu -> Settings -> Ease of Access -> Keyboard (scroll down and it's on the left) -> On-Screen Keyboard). Then I typed bcdedit /deletevalue safeboot (there didn't seem to be a way to use curly brackets). Then I Rebooted, and found that I had left Safe Mode, and everything was back to normal :)

It's one hell of a work-around, but hopefully this helps somebody!

Thanks @Evan! The keyboard thing also happened to me, but using the virtual keyboard did the job. If you press the shift key you'll be able to use curly brackets!

Thank you very much! I am running Server 2016 and didn't realize my Intel board was in IDE until I tried to run two SSD's in Raid0 and was only getting about 400MB/s. I switched to AHCI and was getting "Inaccessible boot device". I used the method described above and it's working now! 1100MB/s.

@ bob and anyone else. To put this simply, this isnt for people with an Active raid array, its for people that have an incorrectly configured bios setting. If you have an active raid array (Raid 0 or some variant there of) this is not the solution for you.

Worked perfectly on a Dell Inspiron 15 7586. Came pre-configured in RAID mode and updated to 970 EVO Plus without the ability to get the Magician to function.
As soon as I completed the operation which took about 3 minutes, everything worked perfectly with no glitches or issues

Hi Marc, you need to use one of those commands not both at once I think, hope that helps

Saved my day. Alternative command is somewhat confusing. I used bcdedit /set {current} safeboot minimal and bcdedit /deletevalue {current} safeboot
Result is that W10 booted with sata settings set to AHCI, Happy!

Thanks for sharing!

Saved my bacon!
I got my ageing (10yrs) Dell T5400 back into life using the full commands.

Very many thanks!

Just performed the procedure on an old Dell D630 fitted with a Kingston SSD that didn't have AHCI enabled.
Went flawlessly and machine now seems to boot a little quicker and feels quicker in operation.

Many thanks!

I just tried to do this but when I restarted it did not reboot in BIOS...
And all of a sudden my password does not work for Windows....
I am locked out...

Any ideas?

This worked for me! Thank you, thank you, thank you.

At some point my intel RST drivers stopped, and I was unable to reinstall the drivers. I thought it was a windows 10 1903 build issue however my system was still on 1809. The problem was at the BIOS level. Some how either through a BIOS update or a dead battery the BIOS storage configuration changed from RAID to IDE.

Without RAID enabled in the BIOS the RST drivers will not install. Also be sure to select the correct driver for your chipset. The newest drivers are not fully backwards compatible!

However even if I manually installed the RST x64 drivers first and then changed the BIOS to RAID the system would not boot.

I opened windows disk management utility and confirmed that the RAID 1 array was broken. Both disks appeared in the drive list, with one showing a warning due to addressing conflict (oh no)

Steps
1) installed the newest intel RST x64 driver that supports the chipset
2) set safeboot per above
3) enabled RAID in BIOS (was IDE)
4) booted to safemode
5) removed safeboot per above
6) checked that intel RST is running YES!
7) verify RAID 1 array (no idea how long the array was broken)

run windows disc management tool and verify RAID now appears correctly as 1 drive

After this Through some update cycle windows stealthily replaced all of the chipset and storage drivers with generic MS drivers.

I hope this helps someone else

to enter bios is a separate step. On my PC it is hitting "DEL" key during reboot.

hi on powershell as admin
PS C:\WINDOWS\system32> bcdedit /set {current} safeboot minimal (ALT: bcdedit /set safeboot minimal)
gives me
ALT: : The term 'ALT:' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At line:1 char:43
+ bcdedit /set {current} safeboot minimal (ALT: bcdedit /set safeboot ...
+ ~~~~
+ CategoryInfo : ObjectNotFound: (ALT::String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

on cmd
C:\WINDOWS\system32>bcdedit /set {current} safeboot minimal (ALT: bcdedit /set safeboot minimal)
Invalid command line switch: /set
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

As previous comment.
on cmd
C:\WINDOWS\system32>bcdedit /set {current} safeboot minimal (ALT: bcdedit /set safeboot minimal)
Invalid command line switch: /set
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

Awesome. This worked.

After activating safe mode and changing the BIOS to AHCI, windows goes into automatic repair mode, could someone help me?

(ALT: bcdedit/set safeboot minimal). No space between bcdedit/set

Worked perfectly on a Dell XPS 13 9360 (i7, touchscreen, SSD). Stupid question: Why doesn't the WIndows automatic repair do this?

Hi everyone, I have the same problem as Vignesh NALLAMILLI. The safeboot is set correctly, in fact, I'm able to boot into the windows' safeboot mode. However, when I change the SATA operation to AHCI, the computer (Alienware m15 with two SSD drives) doesn't boot into the operating system and start a sort of Alienware self-diagnostic mode.
Can anyone help me out with this problem?

This article is a LIFE SAVER!!!!! I'm in the process of migrating a new Windows 10 installation from a 2TB HDD to a 1TB SSD. This is a new (refurbished) Acer desktop system that came with RST with Optane configured in the UEFI settings. So, I followed the steps to switch it to AHCI and Windows 10 now boots. I'm now off to re-clone the HDD to the SSD. :)

For those having problems running the bcdedit commands, the "ALT" commands are supplied as *alternate* commands to use. So, either run the bcedit command that appears *before* the parentheses or run the command INSIDE the parentheses, but not the commands as shown above.

For me, I ran these commands:

bcdedit /set safeboot minimal

(then I rebooted and switched to AHCI)

bcdedit /deletevalue safeboot

THANK YOU for writing such clear and accurate instructions!

Peace...

Worked flawlessly, thank you!

It's 2a.m. God bless you.

@Tom williams thank you very much for better explaining this tuto !
because it did not work because of ALT in the tuto!
and i confirm : it woooooooooorks !!!!! :-D

I have an asus Z97-A motherboard and Intel rapid storage technology is automatically activated in my bios and it automatically activates RAID and i didn't want to.
I wanted AHCI. Every time i reselected AHCI, i had a blue screen crash !

Thanks to this great tuto i can finally! :) i did not believe it and yet it works perfect!
I will see if the file transfers are accelerated in writing with my SSD samsung 850 evo 250go :) because before in RAID i never exceeded 80mb/s for files of 20 - 100go approximately when my ssd can go much higher...

I forgot to specify that i am under windows10 pro 64bits in 1909 and i am in UEFI only. thanks again ;)

This absolutely destroyed my PC. Be careful

Hi, this didn't only half-worked for me. Let me explain:

I have 2 drives installed, one a normal HDD and the other SSD. Both have Win 10 installed so it's dual boot.

While running the PC with SSD as boot drive, I was not able to enter Win 10 after changing the setting in BIOS to ACHI i.e. BSOD. I had to change it back to IDE in order to boot up via the SSD.

I then tried running the PC with my HDD as boot drive. Everything all the steps above went thru smoothly and when I checked in Device Mgr and BIOS setting, ACHI was enabled. So since Win 10 had the ACHI drivers installed, I returned to the BIOS to set my SSD to boot up. It went to BSOD again. So right now for me to use the SSD to boot up my BIOS setting has to be set at IDE.

For information, my SSD was installed with Win 10 in the normal way. The SSD was actually cloned from my HDD since prior to obtaining the SSD, I had upgraded from Win 7 to Win 10 whilst using the HDD. Could this have caused the issue I am facing?

Any help would be appreciated.

Correction, it should be my SSD was NOT installed with Win 10 in the normal way.

I cloned a normal HD onto an SSD, so the setting was at ATA in the bios. Windows ran fine with ATA setting booting from the SSD. I booted normally into Win10, set the safemode, rebooted and changed the BIOS setting to AHCI and booted. Win10 booted into safe mode. In there changed the setting back to normal boot and now its running in AHCI mode.
Awesome! Thank you!