DISCLAIMER: The information in this site is for educational purpose only. The authors of this blog are not responsible for any kind of misuse of this information.

Friday, June 10, 2016

to the Dark Side and Beyond: Upgrading to Win10

Ukuthula !

It was announced that Windows 10 supports bash now.
So, IDFC about my privacy anymore :)

In this post we will upgrade our neglected windows machine to Windows 10.
The internet experiences many problems in upgrading. It also full of risky and not working solutions. This post was written in order to give you more power in debugging your problems.

Today I'll give you tools to debug your error code, specifically debugging error code 0x80070006

First, start the upgrade.
The upgrade process will create a hidden folder in your main drive with some very interesting logs:
$WINDOWS.~BT/Sources/Panther/setupact.log - logs setup actions
$WINDOWS.~BT/Sources/Panther/setuperr.log - logs setup errors

 by inspecting setuperr.log we can identify the specific problem.

when the update fails, it just reboot, writes something about rollback, reboots and then when the old windows installation boots we get a description of the error. The description is very (!) minimalistic and actually says nothing about the real problem.

In case of 0x80070006, the error message is "the installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation".=S

From the setuperr.log we learn that the actual problem was during copying compressed old windows installation. Mmm .. seems like space problem on our main drive. This is in spite of Windows 10 says that we have enough space! Probably someone forgot to count the compressed Windows.old size.
In my case Windows.old consumes ~15GB

I extended my main drive (using a partition tool) and reinstalled. It actually did the magic and windows 10 was installed :)

BTW the discussed hidden folder $WINDOWS.~BT can be deleted safely. It consumes some GBs you can get rid off :)