Windows 7 upgrade to 10 error 0x8007001F - 0x3000D

zbook said:

3) Open administrative command prompt and type or copy and paste:
4) sfc /scannow
5) wmic recoveros set autoreboot = false
6) wmic recoveros set DebugInfoType = 2
7) wmic recoveros get autoreboot
8) wmic recoveros get DebugInfoType
9) net user
10) bcdedit /enum all

11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Getting to some of this now:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\THREINEN-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.
Name="Microsoft Windows 7 Home Premium |C:\\Windows|\\Device\\Harddisk1\\Partiti
on1"'
Property(s) update successful.

C:\Windows\system32>mic recoveros set DebugInfoType = 2
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>mic recoveros get DebugInfoType
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>net user

User accounts for \\THREINEN-PC

-------------------------------------------------------------------------------
Administrator Guest Threinen
The command completed successfully.


C:\Windows\system32>wmic recoveros set DebugInfoType = 2
Updating property(s) of '\\THREINEN-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.
Name="Microsoft Windows 7 Home Premium |C:\\Windows|\\Device\\Harddisk1\\Partiti
on1"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
2


C:\Windows\system32>net user

User accounts for \\THREINEN-PC

-------------------------------------------------------------------------------
Administrator Guest Threinen
The command completed successfully.


C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
displayorder {current}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
recoverysequence {42c3a118-40ed-11e1-98b9-cfb7e23b7a22}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {46fecfd0-40dd-11e1-b49c-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {42c3a118-40ed-11e1-98b9-cfb7e23b7a22}
device ramdisk=[C:]\Recovery\d1bf1c49-d5cd-11e0-ada0-9bf6e51e09
9e\Winre.wim,{42c3a119-40ed-11e1-98b9-cfb7e23b7a22}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\d1bf1c49-d5cd-11e0-ada0-9bf6e51e09
9e\Winre.wim,{42c3a119-40ed-11e1-98b9-cfb7e23b7a22}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {46fecfd0-40dd-11e1-b49c-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US

Device options
--------------
identifier {42c3a119-40ed-11e1-98b9-cfb7e23b7a22}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\d1bf1c49-d5cd-11e0-ada0-9bf6e51e099e\boot.sdi

C:\Windows\system32>

- - - Updated - - -

zbook said:

12) Make sure that there is no over clocking while troubleshooting

13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
Imaging with free Macrium - Windows 7 Help Forums
MACRIUM REFLECT - Create Bootable Rescue USB Drive - Windows 7 Help Forums

14) Create a brand new restore point.
Create System Restore Point in Windows 10
Restore Point - Add "Create Restore Point" to Context Menu in Windows - Windows 7 Help Forums

15) Post images of startup and recovery system failure and Virtual memory / page file settings:
Dump Files - Configure Windows to Create on BSOD - Windows 7 Help Forums

All this is done--images here:

16) Free up space on the Windows drive so that there is > 30 GB free space
Disk Cleanup - Open and Use - Windows 7 Help Forums
Hard Disk Space - Free Up and Recover - Windows 7 Help Forums

I don't think this is possible on my ~55GB SSD. A 1TB SSD arrives tomorrow.

For virtual memory:
a) Place the page file back on the Windows drive.
b) Highlight C: > system managed size
c) Check the box to Automatically manage paging file size for all drives
d) Reboot to maintain settings

The above can be performed after restoring the image.
Please post new images.

These are tools for licensing that can be ran as an extra precaution so that you have the data:
Activation troubleshooting

zbook said:

For virtual memory:
a) Place the page file back on the Windows drive.
b) Highlight C: > system managed size
c) Check the box to Automatically manage paging file size for all drives
d) Reboot to maintain settings

The above can be performed after restoring the image.
Please post new images.

These are tools for licensing that can be ran as an extra precaution so that you have the data:
Activation troubleshooting

zbook, OP SSD is only 55G and is almost full. That is why the Virtual memory is on another disk. He bought a 1T SSD that is arriving soon.
Don't think luke t will have any issue to install Win 10 after he clones the current Win 7 installation on the 1T SSD.

Megahertz said:

zbook, OP SSD is only 55G and is almost full. That is why the Virtual memory is on another disk. He bought a 1T SSD that is arriving soon.
Don't think luke t will have any issue to install Win 10 after he clones the current Win 7 installation on the 1T SSD.

Placing the page file on the Windows drive after the new drive has the restored image:
a) optimizes the ability to create dump files in case there is a BSOD
b) allows the end user to remove all non-windows disk drives during an upgrade

zbook said:

Placing the page file on the Windows drive after the new drive has the restored image:
a) optimizes the ability to create dump files in case there is a BSOD
b) allows the end user to remove all non-windows disk drives during an upgrade

Thanks to you both. I'll plan to "move" my Windows 7 drive onto my new drive as soon as it arrives, and then change the page file settings.

One question--I've never done disk cloning/imaging/moving/whatever-the-right-word-is before, so how do I do it?

zbook said:

17) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


Disk Check - Windows 7 Help Forums

18) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

Read Chkdsk Log in Event Viewer in Windows 10
Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

And finally, ChkDsk results.

Windows drive copy is next.

chkdsk C:

Code:

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Chkdsk E:

Code:

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Chksk F:

Code:

Windows has made corrections to the file system.

zbook said:

chkdsk C:

Code:

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Chkdsk E:

Code:

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Chksk F:

Code:

Windows has made corrections to the file system.

The new drive I ordered turned out to be incompatible with my motherboard. A compatible one arrives later today, but in the meantime, I tried the Windows 10 update again to see if these ChkDsk fixes made any difference. I didn't dig into the log files, but the same error code was generated, and the update again reverted back to Windows 7.

I'll check in here again after I clone my OS to a larger drive, adjust my page file settings, and try the update. Thanks once again everyone for your attention and advice.