2004 update windows 10 error 0x80070002

Here is the result of the first 12 of the set of diagnostic commands:

Microsoft Windows [Version 10.0.18363.900](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning 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>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.900Image Version: 10.0.18363.900[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.18362.900Image Version: 10.0.18363.900[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>sfc /scannowBeginning 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>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 1464320 file records processed. File verification completed. 23372 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 32726 reparse records processed. 1725328 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 32726 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 130505 data files processed.CHKDSK is verifying Usn Journal... 36680152 USN bytes processed. Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 152972403 KB total disk space. 130121860 KB in 524503 files. 333508 KB in 130506 indexes. 0 KB in bad sectors. 1583091 KB in use by the system. 65536 KB occupied by the log file. 20933944 KB available on disk. 4096 bytes in each allocation unit. 38243100 total allocation units on disk. 5233486 allocation units available on disk.C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\MIKEF-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7Updating property(s) of '\\MIKEF-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSEC:\WINDOWS\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\WINDOWS\system32>bcdedit /enum {badmemory}The boot configuration data store could not be opened.The system cannot find the file specified.C:\WINDOWS\system32>

Regards

MF

- - - Updated - - -

Here is the system data image you requested.

- - - Updated - - -

The free space next door has been around for a while....

Code:

The boot configuration data store could not be opened.The system cannot find the file specified.C:\WINDOWS\system32>

Here is the virtual memory window image

- - - Updated - - -

Many thanks again.

I made a recovery disk with the media creation tool and then used it to fix the bcdedit problem.

I ran the bcdedit /enum command:

Microsoft Windows [Version 10.0.18363.900](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>bcdedit /enumWindows Boot Manager--------------------identifier {bootmgr}device partition=E:description Windows Boot Managerlocale en-USinherit {globalsettings}default {current}resumeobject {802243fe-b268-11e9-b045-c8774981695c}displayorder {current} {a329dfd6-4d19-11e7-9d64-74d435b20d2c} {e8ad01ae-b21d-11e9-b043-bd803145626c}toolsdisplayorder {memdiag}timeout 30Windows Boot Loader-------------------identifier {current}device partition=Cath \WINDOWS\system32\winload.exedescription Windows 10locale en-USinherit {bootloadersettings}recoverysequence {e8ad01ac-b21d-11e9-b043-bd803145626c}displaymessageoverride Recoveryrecoveryenabled Yesallowedinmemorysettings 0x15000075osdevice partition=C:systemroot \WINDOWSresumeobject {802243fe-b268-11e9-b045-c8774981695c}nx OptInbootmenupolicy StandardReal-mode Boot Sector---------------------identifier {a329dfd6-4d19-11e7-9d64-74d435b20d2c}device partition=Cath \grub2\g2bootmgr\grub2win.boot.biosdescription Grub 2 For WindowsReal-mode Boot Sector---------------------identifier {e8ad01ae-b21d-11e9-b043-bd803145626c}device partition=Eath \NST\nst_linux.mbrdescription NeoSmart Linuxlocale en-UScustom:250000c2 0C:\WINDOWS\system32>

Comments appreciated

Regards

MF

For posting:

How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


If the post cannot be read > use share links (one drive, drop box, or google drive)


Please make new posts / share links for the steps in post #27.

I have edited this by hand. The post editor trick doesn't work on text copied down from above:

Microsoft Windows [Version 10.0.18363.900](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning 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>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.900

I hope this is easier to read.


Image Version: 10.0.18363.900[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment
Image Servicing and Management toolVersion: 10.0.18362.900
Image Version: 10.0.18363.900[==========================100.0%==========================]

The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannowBeginning 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>chkdsk /scan
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ... 1464320 file records processed.
File verification completed.
23372 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 32726 reparse records processed.
1725328 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
32726 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 130505 data files processed.
CHKDSK is verifying Usn Journal...
36680152 USN bytes processed. Usn Journal verification completed.
Windows has scanned the file system and found no problems.No further action is required.

152972403 KB total disk space. 130121860 KB in 524503 files. 333508 KB in 130506 indexes. 0 KB in bad sectors. 1583091 KB in use by the system. 65536 KB occupied by the log file. 20933944 KB available on disk. 4096 bytes in each allocation unit. 38243100 total allocation units on disk. 5233486 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating
property(s) of '\\MIKEF-PC\ROOT\CIMV2:Win32_OS
RecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.

C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7Updating property(s) of '\\MIKEF-PC\ROOT\CIMV2:Win32_
OSRecoveryConfiguration.Name="Microsoft Windows 10

Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.
C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSE
C:\WINDOWS\system32>wmic recoveros get DebugInfoTypeDebugInfoType7
C:\WINDOWS\system32>bcdedit /enum {badmemory}
The boot configuration data store could not be opened.
The system cannot find the file specified.C:\WINDOWS\system32>

- - - Updated - - -

Microsoft Windows [Version 10.0.18363.900](c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit /enumWindows Boot Manager--------------------identifier {bootmgr}device partition=E:description Windows Boot Manager
locale en-USinherit {globalsettings}default {current}
resumeobject {802243fe-b268-11e9-b045-c8774981695c}
displayorder {current} {a329dfd6-4d19-11e7-9d64-74d435b20d2c} {e8ad01ae-b21d-11e9-b043-bd803145626c}tools
displayorder {memdiag}timeout 30
Windows Boot Loader-------------------identifier
{current}device partition=Cath \WINDOWS\system32\winload.exedescription
Windows 10locale en-USinherit {bootloadersettings}
recoverysequence {e8ad01ac-b21d-11e9-b043-bd803145626c}displaymessageoverride
Recoveryrecoveryenabled Yes
allowedinmemorysettings
0x15000075osdevice partition=C:systemroot \WINDOWS
resumeobject {802243fe-b268-11e9-b045-c8774981695c}nx OptInbootmenupolicy StandardReal-mode

Boot Sector---------------------identifier {a329dfd6-4d19-11e7-9d64-74d435b20d2c}device partition=Cath \grub2\g2bootmgr\grub2win.boot.biosdescription

Grub 2 For WindowsReal-mode Boot Sector---------------------identifier
{e8ad01ae-b21d-11e9-b043-bd803145626c}
device partition=Eath \NST\nst_linux.mbrdescription NeoSmart Linuxlocale en-UScustom:250000c2 0C:\WINDOWS\system32>

When available update the progress with steps #13 - #23.

Many thanks to everyone.

I have now installed the 2004 update.....

Cheers

MF

Nice.

What were the latest steps performed?

Many thanks for your help and advice.

The steps that resulted in fixing the problem were when I used the recovery disk I made to run the Bootrec bcdrepair command......

I had to run the disk partition command at the terminal window to make the disk become active to make bcdedit work again.

That is what cured the problem.

Regards

MF