Fix "The installation failed in the SAFE_OS phase with an error during BOOT operation" - gHacks Tech News

Fix "The installation failed in the SAFE_OS phase with an error during BOOT operation"

The following guide explains how I fixed the error "We couldn't install Windows 10. The installation failed in the SAFE_OS phase with an error during BOOT operation".

I tried to upgrade a system running the RTM version of Windows 10 to the newly released Threshold 2 build. I have done so numerous times on other machines and never ran into issues before.

This time was different however as the following happened: Windows Update picked up the new version just fine, it would download it and start with the installation.

After the reboot it would display a modified troubleshooting page with options to shut down the computer or open advanced troubleshooting options. Regardless of my choice there, it would load the old desktop afterwards reverting all the changes made during installation.

installation failed safe_os phase boot

What weighted even more was that Windows Update would not list the new update as available anymore afterwards. Thankfully, I had already posted information on how to install the update to version 1511 if Windows Update would fail to display it.

The only option that you have then is to download a program from Microsoft that you get on this website and run it to upgrade.

Anyway, I tried that and it resulted in the same issue. Research on the Internet revealed that I was not alone, but most topics were about previous versions of Windows and attempts to upgrade to Windows 10.

The solutions did not help in my case which meant that I had to find the solution on my own.

Fixing the Safe_OS during BOOT operation error

The main hard drive of the computer was encrypted, and while I never experienced any issues in this regard during upgrades, not even from Windows 7 to Windows 10 for instance, I decided to turn off the encryption and attempt the upgrade again.

Turning off the encryption is not as simple as it sounds as I had to decrypt the drive. Thankfully, it was a fast Solid State Drive with only 256 Gigabyte of space which meant that the process completely quickly enough.

I ran Microsoft's upgrade tool again and after some waiting and praying, it turned out that turning off encryption fixed the issue.

The Windows 10 upgrade was installed on the system, and the first thing I did, after modifying preferences that the upgrade reset and changing some default apps, was to encrypt the drive again.

The error may not be that common but if you run into it and use encryption, you may resolve it by disabling encryption for the time of the update.

Summary
Fix
Article Name
Fix
Description
Find out how to fix the Windows 10 upgrade error "The installation failed in the SAFE_OS phase with an error during BOOT operation".
Author
Advertisement

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:


Previous Post: «
Next Post: »

Comments

  1. Andrew said on November 19, 2015 at 6:36 pm
    Reply

    Any idea how to solve the FIRST_BOOT error? When I try upgrading, via MCT or windows update, it installs without an issue, but when it reboots for the “first time” boot it just sticks on the spinning circle boot up screen with no disk activity for hours until I reboot the system, which in turn causes setup to revert back to the original OS.

    I have tried unplugging everything but the keyboard, my next attempt is update all the drivers, and if that doesn’t work, then I might just say f’ it and do a clean install.

    1. Martin Brinkmann said on November 19, 2015 at 6:53 pm
      Reply
      1. Andrew said on November 19, 2015 at 7:06 pm
        Reply

        Thanks Martin, i’ll give those ideas a shot.

  2. gui said on November 19, 2015 at 7:37 pm
    Reply

    hi, i tried googling for some help but nothing relevany came up so i decided to ask here

    i was happily using my w10 as usual, in latest build 1511, nothing extraordinary happened. so i tried to open Word and it didn’t work, a message about not being able to open office, so i decided to restart the pc and as it was going to a reboot a blue screen appears and now my pc is stuck in the recovery menus, i can access all recovery tools of w10 but none work. sfc /scanow prompts an error saying it cant complete the rewuired task, chkdsk said to have fixed some errors and finishes sucessfull. i don’t know what else to try…

    1. Martin Brinkmann said on November 19, 2015 at 7:43 pm
      Reply
      1. gui said on November 19, 2015 at 7:50 pm
        Reply

        no, i wish i could reset it tough
        but inserting a media only gives me the option to format
        is there any way i can trick the installation to do a dirty install keeping all my data?

      2. Martin Brinkmann said on November 19, 2015 at 8:29 pm
        Reply

        I’m afraid I don’t have a solution for the issue you are experiencing. Can you backup the data so that you don’t lose it?

      3. gui said on November 19, 2015 at 8:42 pm
        Reply

        i’m gonna have to find a way to
        i need an extra sata cable to easily do it

  3. Andrew said on November 19, 2015 at 8:40 pm
    Reply

    Martin, Just out of curiosity, are you using your SSD’s hardware encryption or standard bitlocker software encryption?

    1. Martin Brinkmann said on November 19, 2015 at 8:50 pm
      Reply

      I’m using DiskCryptor.

  4. Nerdebeu said on November 20, 2015 at 12:22 pm
    Reply

    I got this error with the updates of the two latest builds “Insiders” (i.e. pre-10586) on my test machine and the drive is not encrypted (and was widely enough space). The only solution I found was clean installs. When I updated in 10586 on my current machine, I feared that the same thing does not happen

  5. nick said on November 20, 2015 at 2:07 pm
    Reply

    Martin,
    I have a system, windows 10 home, with truecrypt.
    I am having the SAFE_OS at BOOT issue also.

    when I FIRST installed windows 10, I had the encryption not installed.
    I then installed it AFTER windows 10 install.

    I have not had update issues since that point, but wiht windows 10 1511, (windows 10 home), I am getting the failure.

    I am in process of decrypting now.
    if that WORKS, then that is a problem, buecause I can’t decrypt every time microsoft comes out with an significatnt uypdate; is there a way to get message to them that they need to fix the reboots, so we don’t have to decrypt?

    with BITLOCKER (microsoft win 10 pro), microsoft seems to STORE the login password, to allow rebooting at installs, during updates, because there is no way they DECRYPTED the drive during the updates; THOSE installs on THOSE machines worked OK.

    so ti seems to be a reboot issue

    i will post an update once it is decrypted
    nick

    1. Martin Brinkmann said on November 20, 2015 at 2:26 pm
      Reply

      Nick, this will be interesting. Thanks!

      1. nick said on November 24, 2015 at 3:48 pm
        Reply

        this was indeed the problem !
        I decrypted;
        ran the upgrade, and it installed ok !
        theen re-encrypted
        but, this poses a problem, if windows 10 can’t decide to boot into safe mode on future updates, but upon booting it needs to give me time to enter the truecrypt password !

        AND, it is interesting as to how it is bypassing or storing the bitiocker password !
        ???

      2. Martin Brinkmann said on November 24, 2015 at 4:09 pm
        Reply

        Now that’s definitely an issue. I have no information about this unfortunately and it is unlikely that we will get an official response from Microsoft.

  6. John said on November 23, 2015 at 2:08 am
    Reply

    My computer was totally kept up to date and has had the same issues, except I’m not encrypted on the drive. Downloaded the direct program from Microsoft with the same results. There must be some glitch in their upgrade.
    DO YOU KNOW if they are working on a fix or are even aware of what is happening to some of us?
    Will those of us affected now be unable to keep our WIN 10 up to date and have virtually ruined our perfectly good copies of WIN 7 by this so called upgrade? I know we can not revert back to WIN 7 after 30 days. Looks like we are screwed unless they are working on a fix.

  7. Matias said on November 23, 2015 at 11:43 am
    Reply

    Martin, “……and changing some default apps, was to decrypt the drive again.” was supposed to be “……and changing some default apps, was to ENCRYPT the drive again.”, no?

    1. Martin Brinkmann said on November 23, 2015 at 12:28 pm
      Reply

      Yes that is right.

  8. Jack Hanna said on March 27, 2016 at 6:36 pm
    Reply

    Samsung 900X laptop had the same issue. Physically removing the WiFi/Bluetooth card did the trick for me. Thanks everyone for the helpful comments!

  9. Wilson said on July 19, 2016 at 6:24 pm
    Reply

    Martin

    An stuck with the error The installation failed in the SAFE_OS phase with an error during BOOT operation”
    Have you got a quick and permanent solution to this problem.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.