0x8007042B-0x2000D - Continuation Thread

BillyNoMates · 18 Aug 2019

@rcairflyer

Im having EXACTLY the same issue as you. Even down to the 28% Complete, then the dreaded restart to black screen and "Undoing changes".

Im going to image my drive, safely stash it on an external overnight tonight, then strip down my AppData and User directories, clean boot, and grab the ISO file on my local drive for the in place upgrade.

I have way too much stuff to just do a clean install (3 different database apps, with god knows how many databases), about 8 IDEs (all with maticulous setups)... The list could go on and on and on.

Hopefully it'll work anyway. It's really strange (and also quite reassuring) that it's the same percentage.

Maybe that's the point it attempts to transfer AppData, and runs in to issues?

zbook · 18 Aug 2019

BillyNoMates ,

These are some routine steps to optimize the upgrade before troubleshooting Panther log files:

Code:

UPGRADE CHECK LIST:
Run through this check list before the next upgrade attempt:

1) remove nonessential hardware
docks
USB devices
printers
headset
speakers
joysticks
projectors
scanners
plotters
portable optical drives (CD, DVD)
microphones
cameras
webcams
smartphones
bluetooth devices
USB drives (other than a windows 10 iso if used for the upgrade)
USB Wireless Mouse or Keyboard Receiver, USB Wireless Network Card
secondary monitors


2) These should be the only attached devices:
wired mouse
wired keyboard
monitor

Any of these that have been done in the past week are not necessary to repeat:


3) open administrative command prompt and type or copy and paste: (repair file system)
chkdsk /r /v 
This may take many hours so plan to run overnight
Find the chkdsk report in the event viewer using the information in this link and post into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html 

4) open administrative command prompt and copy and paste: (repair operating system)
sfc /scannow 
dism /online /cleanup-image /restorehealth 
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

5) update windows (have all recommended updates installed) and reboot after updates

6) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely unistalled)

7) List and uninstall all non-Microsoft firewall software

8) List all Microsoft and non-Microsoft drive encryption software. 
Uninstall all non-Microsoft disk encryption software

9) Run disk cleanup to clean temporary and system files

10) Verify that the drive has > 30 GB free space (At least 25 GB is needed for creating dumps)

11) Place the computer in clean boot:
https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki
https://social.technet.microsoft.com/wiki/contents/articles/29876.how-to-perform-a-clean-boot-in-windows-10.aspx
https://www.tenforums.com/tutorials/41804-perform-clean-boot-windows-10-troubleshoot-software-conflicts.html


12) Detach all SATA devices other than the disk drive that has the Windows operating system
(Make sure that the only disk drive that is attached to the computer at the time of the upgrade attempt is the disk drive containing Windows)
(Other disk drives may be able to be detached by disconnecting cables or if necessary to remove the drive from the computer)

13) Make sure that there is no metered connection:  https://support.microsoft.com/en-us/help/17452/windows-metered-internet-connections-faq

BillyNoMates · 19 Aug 2019

Done
Done
Done, no issues found.

When running

Code:

sfc /scannow

I get the following relevant part in my error log:

Code:

2019-08-19 13:10:46, Info                  CSI    000067c8 [SR] Cannot repair member file [l:9]'mfc80.dll' of Microsoft.VC80.MFC, version 8.0.50727.6229, arch x86, versionScope neutral, pkt {l:8 b:1fc8b3b9a1e18e3b}, type [l:5]'win32' in the store, hash mismatch
2019-08-19 13:10:46, Info                  CSI    000067cb [SR] Cannot repair member file [l:9]'mfc80.dll' of Microsoft.VC80.MFC, version 8.0.50727.6229, arch x86, versionScope neutral, pkt {l:8 b:1fc8b3b9a1e18e3b}, type [l:5]'win32' in the store, hash mismatch
2019-08-19 13:10:46, Info                  CSI    000067cc [SR] This component was referenced by [l:18 ml:19]'Windows Foundation'

I'm unable to find a fix (I've installed "SQL Server Express 2008", and "Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)", both of which should contain the library, but the issue persists). I'm also not entirely sure that these issues are related anyway.

I've run both (in this order):

Code:

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.799

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

Code:

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.799

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Can't do... Updates don't work, thus the error.
Done
Done (never had any)
Done. Had VeraCrypt, but it was just a volume file. But that's gone now too.
Done
C: Drive (system drive) has ~64GB free... My Windows folder is about 30GB though...
Done
Done
Done

UPDATE: When trying again to update through Windows Update, it fails to install "KB4512501", with error "0x800f0922". Which according to - https://support.microsoft.com/en-us/...llation-errors - means:

This error might mean that your PC couldn't connect to the Windows Update servers. If you're using a VPN connection to connect to a work network, disconnect from the network and turn off the VPN software (if applicable) and try upgrading again.

The error could also mean there isn't enough free space in the System Reserved partition. You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition.

Which is interesting... I can discount the first bit, as it can access the network just fine (I also installed it with the offline installer - https://www.catalog.update.microsoft...aspx?q=4512501). But it lead me to fire up my partition manager, and all I see is:

0x8007042B-0x2000D - Continuation Thread-cqkh2-4yreodhkl2mdgw_q.png

No system reserved partition... At least not an obvious one... Could this be the source of my woes?

zbook · 19 Aug 2019

BillyNoMates,

Create a new thread and post the new link into this thread.

For all steps please post images and or share links 9one drive, drop box, google drive)
(For example: results from chkdsk /r /v)

Find a flash drive that you can format ( > or = 8 GB)

Create a bootable Windows 10 iso version 1803 or build 17134:

Windows Download - #1 Windows ISO Download Source
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)

Perform an in place upgrade repair with the same version.

If the identical iso in place upgrade repair is successful then repeat the in place upgrade repair with either 1809 or 1903.

If the identical iso in place upgrade repair is not successful then perform the following steps:

Run setupdiag: https://docs.microsoft.com/en-us/win...rade/setupdiag

Download and install: Everything

Launch the application and search for any of these files and folders: (only logs from the prior week)

Code:

PANTHER logs
C:\Windows\Panther

folders:
\$Windows.~bt\sources\panther
\$Windows.~bt\Sources\Rollback
\Windows\Panther
\Windows\Panther\NewOS

setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
Windows\Logs\Mosetup
Setupapi.offline.log

There are log collectors used in another forum room.
Run each V2 and DM and upload the results into the new thread:

BSOD - Posting Instructions

BillyNoMates · 19 Aug 2019

You don't think this is related to my 100MB (49MB free) EFI System Partition.

I see that it's recommended to be 500-600+ MB for updates/upgrades?

- - - Updated - - -

zbook said:

Find a flash drive that you can format ( > or = 8 GB)

Create a bootable Windows 10 iso version 1803 or build 17134:

Windows Download - #1 Windows ISO Download Source
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)

Perform an in place upgrade repair with the same version.

Should I be booting from the USB drive? Or running it from inside windows, from the ISO file?

Your description seems to suggest creating a bootable USB, mounting the Windows 10 Pro 1803 ISO on it, restarting the PC, booting from the USB, and installing from there?

But then - Repair Install Windows 10 with an In-place Upgrade - Says:

You will only be able to do a repair install of Windows 10 from within Windows 10. You will not be able to do a repair install at boot or in Safe Mode.

So I'm a little confused..?

- - - Updated - - -

As requested:

0x8007042B-0x2000D - Continuation Thread

zbook · 19 Aug 2019

When performing an in place upgrade repair please use a bootable Windows 10 iso.
Open file explorer and launch setup.exe within file explorer.

If windows 10 uprade troubleshooting fails backup options are:
a) clean install
b) continue to use old version without updates (increased security risks, etc.)
c) reset save files (reinstall drivers and applications)

Booting using the iso is for windows recovery, custom, and clean install.

For in place uprade repairs do not boot using the iso.
Instead open file explorer > this PC > C: > launch setup or setup.exe

Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

Open administrative command prompt and copy and paste:

Code:

bcdedit /enum all
reagentc /info
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4 
det par
sel par 5
det par
sel par 6
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par

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

zinou · 20 Aug 2019

As @zbook suggested in his previous poste. Upload the log files so that we can get more details about the problem.

BillyNoMates · 20 Aug 2019

Success!

I used the tool found at:

Microsoft Windows and Office ISO Download Tool

Downloaded the 1803 professional iso file (my current version), navigated in to it with explorer, ran setup.exe, and it worked successfully.

I then proceeded to download each subsequent update in turn from the same ISO tool, and they each updated successfully after that.

Im currently on 1903, updating it from the slow ring of the insider program, so I can take advantage of WSL 2.

Thanks for your help zbook. It really worked. :)

zbook · 20 Aug 2019

That's great news.
You are very welcome.

patrickdrd · 20 Sep 2019

I'm having the same issue

Code:

identifier              {4eb1a836-0c04-11e8-88cf-9db0809a6163}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {c1f47fef-65a0-11e8-94fc-8ee1ac7cfbcc}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume3
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Local

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {8c2db71a-c3ee-4ed8-b0aa-990b00369c02}
ramdisksdidevice        partition=C:
ramdisksdipath          \Aomei\AomeiBoot.sdi

Device options
--------------
identifier              {c1f47ff0-65a0-11e8-94fc-8ee1ac7cfbcc}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume2
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {d02f3003-3401-4137-a7ba-f2e50a850c1f}
ramdisksdidevice        partition=C:
ramdisksdipath          \Aomei\AomeiBoot.sdi

C:\Windows\System32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition2\Recove
ry\WindowsRE
    Boot Configuration Data (BCD) identifier: c1f47fef-65a0-11e8-94fc-8ee1ac7cfb
cc
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.


C:\Windows\System32>diskpart

Microsoft DiskPart version 10.0.17134.1

Copyright (C) Microsoft Corporation.
On computer: D10180W1874

DISKPART> lis dis

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB  1024 KB        *

DISKPART> lis vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 B  No Media
  Volume 1         Recovery     NTFS   Partition    499 MB  Healthy
  Volume 2     C   SYSTEM       NTFS   Partition    167 GB  Healthy    Boot
  Volume 3     D   DATA_WORK    NTFS   Partition     70 GB  Healthy
  Volume 4                      FAT32  Partition    100 MB  Healthy    System

DISKPART> sel dis 0

Disk 0 is now the selected disk.

DISKPART> det dis

Micron 1100 SATA 256GB
Disk ID: {DB2DED23-E4F4-4CAE-B932-DDCF0DDA3EB0}
Type   : SATA
Status : Online
Path   : 0
Target : 1
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C00T01L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1         Recovery     NTFS   Partition    499 MB  Healthy
  Volume 2     C   SYSTEM       NTFS   Partition    167 GB  Healthy    Boot
  Volume 3     D   DATA_WORK    NTFS   Partition     70 GB  Healthy
  Volume 4                      FAT32  Partition    100 MB  Healthy    System

DISKPART> lis par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved           128 MB    17 KB
  Partition 2    Recovery           499 MB   129 MB
  Partition 3    System             100 MB   628 MB
  Partition 4    Primary            167 GB   728 MB
  Partition 5    Primary             70 GB   167 GB

DISKPART> sel par 1

Partition 1 is now the selected partition.

DISKPART> det par

Partition 1
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 17408

There is no volume associated with this partition.

DISKPART> sel par 2

Partition 2 is now the selected partition.

DISKPART> det par

Partition 2
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 135266304

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 5         Recovery     NTFS   Partition    499 MB  Healthy    Hidden

DISKPART> sel par 3

Partition 3 is now the selected partition.

DISKPART> det par

Partition 3
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 658505728

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 4                      FAT32  Partition    100 MB  Healthy    System

DISKPART> sel par 4

Partition 4 is now the selected partition.

DISKPART> det par

Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 763363328

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2     C   SYSTEM       NTFS   Partition    167 GB  Healthy    Boot

DISKPART> sel par 5

Partition 5 is now the selected partition.

DISKPART> det par

Partition 5
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 180084926976

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3     D   DATA_WORK    NTFS   Partition     70 GB  Healthy

DISKPART> sel par 6

The specified partition is not valid.
Please select a valid partition.

There is no partition selected.

DISKPART> det par

There is no partition selected.
Please select a partition and try again.

DISKPART> sel dis 1

The disk you specified is not valid.

There is no disk selected.

DISKPART> det dis

There is no disk selected to list details for.
Please select a disk and try again.

    Displays the properties of the selected disk and the list of volumes on
    the disk.

Syntax:  DETAIL DISK

    A disk must be selected for this operation to succeed.

Example:

    DETAIL DISK

DISKPART> lis par

There is no disk selected to list partitions.
Select a disk and try again.

DISKPART> sel par 1

There is no disk selected to set the partition.
Select a disk and try again.

DISKPART> det par

There is no disk selected.
Please select a disk and try again.

DISKPART> sel par 2

There is no disk selected to set the partition.
Select a disk and try again.