Yes navigate to one of the files and use it. One of the copies not in Macrium. If a document open it, if a picture view it. Just want to be sure they are intact and usable. You put a lot of effort into getting them.
Oh, 1703. I thought you were on 1709. It has to be same version.
So then the decision point stands, try folder backup or clean install.
I recognize I sound cold, I don't mean to be, but we both know with some installations of Windows some just can't be fixed.
The new users folder was opened on E:
Camera Roll
Saved Pictures
were both empty
Videos:
Captures
was empty
Music
empty
3d objects displayed
bulldozer to windmill
Contacts
empty
Desktop
many folders and files displayed
owner (this was the folder placed on the desktop after the Microsoft store backup and restore)
This owner folder has pictures, music,
I was able to open documents and view an important document.
An in place upgrade had failed with the identical iso (1703) and was not recently tried.
The Windows update troubleshooter was ran and completed.
For software distribution:
Most of these files were deleted:
Prefetch
Temp
%temp%
For services.msc:
bits > running
cryptographic services > running
windows installer > running
windows update > running
The latest Media creation tool was downloaded (1803) > windows 10 setup > getting a few things ready > accept applicable notices and license terms > getting a few things ready > upgrade this PC now > getting a few things ready >
Modern Setup Host
Modern setup host has stopped working.
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
The MCT failed to upgrade Windows 1703 > 1803
I don't know enough about how you use your PC to comment on the empty folders. Lots of people don't have music or videos on their device. Contacts is a leftover from earlier windows. I think the only thing it is used for now is Faxing, at least that is where my contacts are in Windows 7 for faxing.
Not sure where you store your Pictures. Makes sense Camera roll is empty, think in the context of a PC that is for shots from Web cam. Mine is empty too. I use my own Picture folders and not the Windows Library per say.
You must know where your Pictures are.
I would be suspect even if 1803 upgrade had worked, again from all the issues you have described. I would get out the manual and clean install. I say get out the manual as you will want to engage the 32GB drive, I assume. That probably means set the raid to 0 before installation begins.
One of the steps to a successful clean install is deleting all partitions on 750GB. Sure you don't have to but .......
When you clean install just have your 750 and 32GB installed.
Since you will be deleting all partitions on the 750 your data on the 750GB will be removed. <<<<=====
Once you have Windows installed and the Raid working you can consider next steps. By this I mean one large C: with data or a smaller C: and D: for personal data.
The Intel RST software /driver required a reboot to complete the installation.
A Windows upgrade was attempted and it failed.
The Windows update troubleshooter was ran.
Many hours were spent with Microsoft level 1 and 2 to see if they had an ideas on how to fix.
win + r > prefetch > deleted
wind + r > temp > deleted
win + r > %temp% > deleted
services.msc >
bits
cryptographic services
windows installer
windows update
all stopped then started
The contents of the software distribution folder were deleted.
system32 > catroot > contents deleted
The computer was placed in clean boot.
It was rebooted and failed to reboot displaying:
No bootable image found; notebook will be shut down.
Multiple power on and power off in succession failed to open the computer's windows advanced troubleshooting menu.
The method that worked to fix the boot was control + I > automatic repair > wall paper > logon > desktop.
Every reboot after this step continued to display no bootable image found. Notebook will be shut down.
And again the boot was fixed by control + I
Using the identical Windows 10 iso (1703) repetitively displayed:
Modern Setup Host
Modern Setup Host has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
A windows 10 iso version 1803 was downloaded to the desktop and ran.
It displayed the same popup:
Modern Setup Host
Modern Setup Host has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
The Panther logs were viewed and they displayed error code:
80080005 > 0xC1900108 0x90017
The Intel RST software / driver had been downloaded and installed multiple times.
Each time the options were either to remove the software/driver or repair.
The repair was always chosen. It was never fully uninstalled with an attempted reinstall.
Each time it required are reboot to complete the installation.
Launching Intel RST each time displayed:
Intel RST acceleration was never able to be disabled to convert the HD from RAID 0 to a regular HD.
Multiple additional methods were attempted to get the WIndows to upgrade.
A fresh copy of Malwarebytes was uninstalled.
Using Windows 10 1803 setup created a more usable error message:
We couldn't upgrade the system reserved partition.
The EFI partition was then viewed and problems were found.
See post # 58 with the found files.
These appear to be the same files found in the EFI partition?
If so the file size is substantial and may be taking up the needed space for the Windows upgrade.
This information has not yet been found in the Panther log files.
continued
If the computer can be upgraded from 1703 to 1803 then problems with potential loss of folders or files may not happen.
There are two Users backup folders now on the 4 TB external HD:
Wondering if all of the files
File0000.CHK
File0001.CHK
File0002.CHK
can be uninstalled without any problems or loss of important files?
Are these chk files related?
The chk files in the EFI partition are consuming 20 KB.
If they are removable it may then allow a fix of the Windows upgrade failure: We couldn't upgrade the system reserved partition.
The post that you had made was missed while continuing the post.
The uncertainty with the backup of the Users is the concern as there were so many duplicate file names that had different dates and different sizes.
If a Windows upgrade can fix the corruption then it would not put any files at risk.
If a Windows upgrade cannot fix the corruption then the disk sanitization is the next step.
The proper restoration of the Users folders with all of the problems was never done is likely related to the multiple duplicate files.
For one of the Windows upgrade failures Microsoft created the Administrator account and attempted to remove languages and fonts from the EFI partition. The computer crashed. A chkdsk was ran after the crash and it had displayed problems. So the crash could happen again.
The Microsoft supported suggested using a Windows backup via settings. This I had never done. He indicated that it saves folder/files and not the problems with the operating system. If this is correct how is this done?
The dates of the chk files in the EFI partition are 3 15 2018.
I no longer remember what had happened on that date.
Okay. Boot up Kyhi's recovery disk and use Folder backup to backup folder users\aaaaaaa. You can first try at that high level (users\aaaaaa) and if errors occur you can move down a level and backup individual folders like documents and Pictures.
Tonight I accidentally came across information in chkdsk that explains the problems that are in the EFI partition.
When chkdsk has problems with fixing / recovering files it creates the chk files.
Macrium was not able to make a backup image when it reported an error.
The error was a cluster run error.
This required the use of diskpart, the labeling of a hidden partition and then running chkdsk /r on the partition.
This was the EFI partition.
This had been run many months ago and I did not know what to do when it prompted for Y or N and had chosen Y.
The log file below also displayed the system reserved partition had been on the storage drive.
Code:Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>diskpart Microsoft DiskPart version 10.0.15063.0 Copyright (C) Microsoft Corporation. On computer: DESKTOP-BH9NBPV DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 698 GB 0 B * Disk 1 Online 931 GB 1024 KB Disk 2 Online 58 GB 26 GB DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 E DVD-ROM 0 B No Media Volume 1 C NTFS Partition 698 GB Healthy Boot Volume 2 Recovery NTFS Partition 450 MB Healthy Hidden Volume 3 FAT32 Partition 99 MB Healthy System Volume 4 D System Rese NTFS Partition 500 MB Healthy Volume 5 F New Volume NTFS Partition 931 GB Healthy Volume 6 G ESD-USB FAT32 Removable 32 GB Healthy DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 450 MB 1024 KB Partition 2 System 99 MB 451 MB Partition 3 Reserved 16 MB 550 MB Partition 4 Primary 698 GB 566 MB DISKPART> select volume 3 Volume 3 is the selected volume. DISKPART> detail volume Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- * Disk 0 Online 698 GB 0 B * Offline : No DISKPART> assign letter=b DiskPart successfully assigned the drive letter or mount point. DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 E DVD-ROM 0 B No Media Volume 1 C NTFS Partition 698 GB Healthy Boot Volume 2 Recovery NTFS Partition 450 MB Healthy Hidden * Volume 3 B FAT32 Partition 99 MB Healthy System Volume 4 D System Rese NTFS Partition 500 MB Healthy Volume 5 F New Volume NTFS Partition 931 GB Healthy Volume 6 G ESD-USB FAT32 Removable 32 GB Healthy DISKPART> exit Leaving DiskPart... C:\Windows\system32>chkdsk /r B: The type of the file system is FAT32. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) y Volume dismounted. All opened handles to this volume are now invalid. Volume Serial Number is 5C23-338D Windows is verifying files and folders... The size of the \EFI\HP\SystemDiags\SystemDiags.log entry is not valid. \EFI\Boot\bootx64.efi is cross-linked on allocation unit 125. Cross link resolved by copying. File and folder verification is complete. Convert lost chains to files (Y/N)? y 20480 bytes in 3 recovered files. Windows is verifying free space... Free space verification is complete. Windows has made corrections to the file system. No further action is required. 99,614,720 bytes total disk space. 155,648 bytes in 7 hidden files. 71,680 bytes in 54 folders. 94,574,592 bytes in 191 files. 4,811,776 bytes available on disk. 1,024 bytes in each allocation unit. 97,280 total allocation units on disk. 4,699 allocation units available on disk.
The above is the log file that matches the date of the chk files in the EFI partition in the image.
So those are boot files?
Can they be deleted?
That may free up the space needed to perform Windows upgrade to 1803 and not get the "We couldn't upgrade the system reserved partition"
Last edited by zbook; 18 Sep 2018 at 01:31.
If your EFI partition is suspect you can delete and recreate.
How to make GPT volume bootable
We maybe working at cross purposes.
I thought you were going to use Macrium to backup your users\aaaaaa folder, not Image your bad Windows installation.
Quote
