Updating to 10 Pro from 7 Ultimate 64x > 0x80070011 - 0x2000D

dalchina · 13 Jun 2018

This tutorial
Upgrade to Windows 10 | Windows 10 Tutorials
and the many links under Resolve Windows 10 upgrade errors and the link preceding that gives a great resource to fix upgrade problems, and a variety of approaches, including elementary practical steps, MS sites and details of logs you can inspect.

Noting
Safe OS phase: A recovery partition is configured, Windows files are expanded, and updates are installed. An OS rollback is prepared if needed. Example error codes: 0x2000C, 0x20017.

Do you have any unallocated space on your disk?
Please post a screenshot of your partition layout.

ZFPuhi · 13 Jun 2018

@dalchina Attaching a screenshot as you requested, also I did check the topic that you linked (both of them) and unfortunately I was not able to find related to the '0x80070011' and '0x2000d' issue unfortunately.

Updating to 10 Pro from 7 Ultimate 64x > 0x80070011 - 0x2000D-a959ab3f20a4547f3154f65f27f0a8c6.png

@cereberus After re-reading the topic 2 times I can see that I should skip the first part and start from "Part Two" , but will need to re-read it more times in order to understand it properly.

Edit: I re-read the topic again 'cereberus ' and from what I can see it will install a windows on the assigned partition, but not sure what will happen if I apply that on already active not formatted disk (the current windows disk). Do you have any in sign on such operation?

dalchina · 13 Jun 2018

You have 2 partitions marked 'Active'... and there is no unallocated space for Windows to create needed new partitions, which could be a problem. (Others have said C: would be shrunk automatically- I've no evidence one way or the other, so look for any comment on that). However that matches with comment made earlier about your error message.

@dalchina Attaching a screenshot as you requested, also I did check the topic that you linked (both of them) and unfortunately I was not able to find related to the '0x80070011' and '0x2000d' issue unfortunately.

There's a lot of practical guidance there, and did you inspect the log files described in that?

ZFPuhi · 13 Jun 2018

dalchina said:

You have 2 partitions marked 'Active'...

The size of the first Active is 100 MB which is the safe partition part of the SSD.

Edit: by the sentence above not sure if it's clear but Whenever I have an SSD Disk it automatically creates a "safe" partition with like 100 MB of space which is part of the SSD, and maybe because the windows is installed on my SSD is the reason behind why it is set as "Active" also not sure.

dalchina · 13 Jun 2018

One of the practical guidelines is to remove or disconnect other disks..

ZFPuhi · 13 Jun 2018

@dalchina

One of the suggestions was to remove the other SSD Disk (the 111 GB one which does not have the windows on), which I did but I still encountered the issue. As for your edit above I am not quite sure what you mean by "Windows to create needed new partitions" since in this case we are trying to perform an upgrade on an existing and running Windows 7 up to Windows 10, not quite sure what kind of re-creation of partitions is needed. Also I did check the guidance there and unfortunately there wasn't enough helpful information that I haven't yet tried which could be even remotely connected to my issue. As for the log file could you be more specific exactly which one should I check , so that I can inspect it now (since it might still contain information from the last time i tried to update few days ago).

dalchina · 13 Jun 2018

Windows 10 uses a number of partitions, not just one. This differs between MBR and EFI installations.
You can see these in the diagrams here:
BIOS/MBR-based hard drive partitions | Microsoft Docs
UEFI/GPT-based hard drive partitions | Microsoft Docs

It is useful to understand these if you ever run into certain problems or need to manage partitions.

Given that, you should now be able to understand that in upgrading, Windows needs to create new partitions.

Following links in the Tutorial I quoted, here is one document referenced which lists log files.
Log files - Windows IT Pro | Microsoft Docs

Try setuperr.log for starters.

Basics-
Create a disk image of your current system before attempting to upgrade. E.g. Macrium Reflect (free).
There are plenty of reports of bad outcomes in upgrading to 1803.
We constantly urge users to use disk imaging routinely.

a. uninstall any security software
b. disconnect all but your system drive
c. create sufficient unallocated space on your disk- say 1Gb should be plenty
d. download and create a bootable Win 10 disk
e. attempt the upgrade

ZFPuhi · 13 Jun 2018

@dalchina

I have just checked the 'setuperr.log' file from the following locations:

C:\Windows\Panther
C:\Windows\Panther\UnattendGC
C:\Windows\System32\sysprep\Panther

But all of them were empty no information inside. As for the steps from A ~ E could you please clarify why I have to disconnect all of the disks in order for the upgrade to be "successful" .

Looking forward to hearing back from you.

dalchina · 13 Jun 2018

It should not be necessary to do that in a trouble-free situation, but where people have problems, it is a recommended precautionary step.

In particular, you have two active partitions, normally indicative of two OS installations or remnants thereof. This could cause problems.

Further, where the system disk is completely allocated, should there be spare space on other disks, the new partitions Win 10 creates may appear on other disks.