[SOLVED] We can't tell if your PC has enough space to continue installing Windows 10.

nemesis19

Contributor
Joined
Apr 5, 2018
Posts
17
Location
Southwest France
Hi to All,
I hope there is somebody here that can help me sort out this Win10 1703 - 1709 Update problem on an Asus R900VM.

PC Specs

Processer : Intel Core i7-3610QM @ 2.30 GHz
Ram : 16 Gb
Graphics : Intel HD Graphics 4000
Nvidia GeForce GT 630M
HDD : Seagate Baracuda 3Tb Divided into C:/OS approx 1.2Tb and D:/Data approx 1.6Tb plus various other partitions (EFI, etc) 27Gb

There is about 900Gb free space on the C: Drive.

Update gets to the stage where it is verifying the amount of free space (Approx 82%) and returns with the error 0x800703f1 We can't tell if your PC has enough space to continue installing Windows 10. Try restarting setup 1703 to 1709.
This update is trying to pass three or four times a day to no avail for the last couple of months.

I have carried out the instructions above, sfc /scannow, Dism /Online /Cleanup-Image /RestoreHealth and the SFCFix, the update still stalls at the same stage.

CBS.zip

Hoping that someone can help,
best Adrian W.
 
>Hi, back again,

I have done a chkdsk which found no errors.

I've also downloaded the ISO onto a USB stick and tried the update from there, still fails on the checking available disk space.

Here's the setuperr.log

Code:
2018-04-06 18:45:52, Error                 CONX   0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

2018-04-06 18:47:07, Error                 IBSLIB BCD: Failed load key BCD00000000. Flags: 0x40 File: \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD Status: c000014c[gle=0x00000003]
2018-04-06 18:47:07, Error                 IBSLIB BCD: Failed to load hive into key BCD00000000 from \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD. Status: c000014c[gle=0x00000003]
2018-04-06 18:47:07, Error                 IBSLIB BCD: Failed to add system store from file. File: \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD Status: c000014c[gle=0x00000003]
2018-04-06 18:47:07, Error                 MOUPG  CDlpActionDiskSpaceReq::CalculateRequiredDiskSpaceInstallReq(1752): Result = 0x800703F1[gle=0x00000003]
2018-04-06 18:47:07, Error                 MOUPG  CDlpActionDiskSpaceReq::ExecuteInstallReq(1279): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CDlpActionDiskSpaceReq::ExecuteRoutine(501): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDiskSpaceAction> > > >::Execute(441): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CSetupManager::ExecuteTask(2170): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CSetupManager::ExecuteTask(2133): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CSetupManager::ExecuteInstallMode(715): Result = 0x800703F1
2018-04-06 18:47:07, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(347): Result = 0x800703F1
2018-04-06 18:47:10, Error                 MOUPG  CSetupManager::Execute(237): Result = 0x800703F1
2018-04-06 18:47:10, Error                 MOUPG  CSetupHost::Execute(375): Result = 0x800703F1

Anyone any ideas ?

best Adrian W.
 
Hello and welcome to Sysnative!

Can you show me a screenshot from Disk Management?
Is this a multiboot system? If yes, please detach all other HDDs and try the upgrade again. Disconnect all peripheral devices during the upgrade.
What's your antivirus/internet security product? Have you tried completely removing it prior to the upgrade?
 
Hello softwaremaniac,

no it's not a multiboot system, only one HDD divided into several partitions, no peripherals connected apart from a usb mouse and avast removed prior to upgrade.

Capture of disk management
Disk_Management.jpg

Best, Adrian W.
 
Hello,

please provide logs for me.

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
Your CBS.log is very interesting.
Please do the following so I can gather more info:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Here it is

Code:
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-04-07 17:06:32.630
Microsoft Windows 10 Build 15063 - amd64
Using .txt script file at C:\Users\Adr_isa\Desktop\SFCFixScript.txt [0]








FileScan::
[0: 1] C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.962_none_1bd03c6fead52ca4\usocore.dll
File is untraceable.
 Found: TZBtg8sNfHt3+xTmJAKoAJTCdcdW7/gQmjQVPAntUzs=
 Version number not available.
Trace not available.






[1: 1] C:\Windows\WinSxS\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.0_none_10223888c44c31c4\updatehandlers.dll
File is untraceable.
 Found: FoGQ8R0kI+uu2fZsjDNaZ7xOm4ncIwpgKtOIMopB2p0=
 Version number not available.
Trace not available.






[2: 1] C:\Windows\WinSxS\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.962_none_5f5809f22d66fea4\dosvc.dll
File is untraceable.
 Found: 52Qcpi1N020JzQp8vCo8cgnOq0hD6+tPkvQ5iMOeWVY=
 Version number not available.
Trace not available.






[3: 1] C:\Windows\WinSxS\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.962_none_940c4819f1df88e9\updatehandlers.dll
File is untraceable.
 Found: WuUFYxEGRXscdJIXmFUec/oPzrI2NVK+tkrJh3AUNtw=
 Version number not available.
Trace not available.






[4: 1] C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.0_none_97e62cdebd41d57f\usocore.dll
File is untraceable.
 Found: CRJ98diFM+6xd8OFg9UDVt4fmuMZG8UhX768QLqiomk=
 Version number not available.
Trace not available.






[5: 1] C:\Windows\WinSxS\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.962_none_43e045b30ffb89be\wuauclt.exe
File is untraceable.
 Found: Dueonpf70R0WICLp2tkjHDPV3aWOl8634SxuLxvSSvc=
 Version number not available.
Trace not available.






[6: 1] C:\Windows\WinSxS\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.0_none_db6dfa60ffd3a77f\dosvc.dll
File is untraceable.
 Found: U2HPUiJxXxYY5hQSPl5i+ay93ASrtoYIFAha6EBsMpY=
 Version number not available.
Trace not available.






[7: 1] C:\Windows\SoftwareDistribution\Download\3bbe913523b063ccd6f178f733c3e742\amd64_Microsoft-Windows-Client-Features-Package~~AMD64~~10.0.16299.15\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.16299.15_none_ed464d1a38296141\dosvc.dll
File is untraceable.
 Found: HB2SggX9lyKxKZF6OBOqt74RxeqLa8MDy5PIBYrTRrs=
 Found: 10.0.16299.15
Trace not available.






[8: 1] C:\Windows\SoftwareDistribution\Download\3bbe913523b063ccd6f178f733c3e742\amd64_Microsoft-Windows-Client-Features-Package~~AMD64~~10.0.16299.15\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.16299.15_none_a9be7f97f5978f41\usocore.dll
File is untraceable.
 Found: j4wfNH1CQ0Imny+5rxvxVS0pW4LBPez+mnyxYk7FTTc=
 Found: 10.0.16299.15
Trace not available.






[9: 1] C:\Windows\SoftwareDistribution\Download\3bbe913523b063ccd6f178f733c3e742\amd64_Microsoft-Windows-Client-Features-Package~~AMD64~~10.0.16299.15\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.16299.15_none_21fa8b41fca1eb86\updatehandlers.dll
File is untraceable.
 Hash not available.
 Version number not available.
Trace not available.






[10: 1] C:\Windows\SoftwareDistribution\Download\3bbe913523b063ccd6f178f733c3e742\amd64_Microsoft-Windows-Client-Features-Package~~AMD64~~10.0.16299.15\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.16299.15_none_d1ce88db1abdec5b\wuauclt.exe
File is untraceable.
 Found: epMFDsoX01DKJLQ5+ia4g/aFKyX0VMnBReQHShzoTL4=
 Found: 10.0.16299.15
Trace not available.






[11: 1] C:\Windows\WinSxS\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.0_none_bff63621e2683299\wuauclt.exe
File is untraceable.
 Found: RKjnP6xaEgPGoHakQikUCl3/yQCGvRJBh53sHCepSi8=
 Version number not available.
Trace not available.






[12: 1] C:\Windows\SoftwareDistribution\SIH\bin\cbs\{F8249BD8-2608-11E8-8517-705A0F491A19}\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.962_none_5f5809f22d66fea4\dosvc.dll
File is untraceable.
 Found: gt8DqhqawDe4Tr/lWV5w9NtGHhXbQjFC94EQTq+gtHk=
 Found: 10.0.15063.909
Trace not available.






[13: 3] C:\Windows\System32\usocore.dll
File is untraceable.
 Found: sEoKBDIT2QpfNatk8XrEee5xMUYo2pfwFQYNxiUmWS4=
 Found: 10.0.15063.966
Trace not available.


 [C:\Windows\WinSxS\Temp\InFlight\991a94d2d4c9d301200a00005c0c9822\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.966_none_1bd43d97ead19200\usocore.dll]
 [C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.994_none_1bb1cd3feaebb325\usocore.dll]




[14: 3] C:\Windows\WinSxS\Temp\InFlight\991a94d2d4c9d301200a00005c0c9822\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.966_none_94104941f1dbee45\updatehandlers.dll
File is untraceable.
 Found: 49KNjDnNyuXXW8CgJOBS5oiDk5ZSoTHD+/LECk0mjuM=
 Found: 10.0.15063.966
Trace not available.


 [C:\Windows\System32\updatehandlers.dll]
 [C:\Windows\WinSxS\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.994_none_93edd8e9f1f60f6a\updatehandlers.dll]




[15: 5] C:\Windows\System32\dosvc.dll
File is untraceable.
 Found: gt8DqhqawDe4Tr/lWV5w9NtGHhXbQjFC94EQTq+gtHk=
 Found: 10.0.15063.909
Trace not available.


 [C:\Windows\WinSxS\Temp\InFlight\991a94d2d4c9d301200a00005c0c9822\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.966_none_5f5c0b1a2d636400\dosvc.dll]
 [C:\Windows\WinSxS\Temp\PendingDeletes\9f834d0dedbed30190030000dc1bf431.dosvc.dll]
 [C:\Windows\WinSxS\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.994_none_5f399ac22d7d8525\dosvc.dll]
 [C:\Windows\WinSxS\Temp\PendingDeletes\b451c5bfd7c9d301ee1800005c0c9822.dosvc.dll]




[16: 2] C:\Windows\System32\wuauclt.exe
File is untraceable.
 Found: b43fB6RPHeZMX04xjl4uEzMP52SxYdmK/rT0DvScQc8=
 Found: 10.0.15063.936
Trace not available.


 [C:\Windows\WinSxS\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.994_none_43c1d6831012103f\wuauclt.exe]
FileScan:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-04-07 17:06:56.325
Script hash: bbsopeNCbQ5toJ7+VJdFSX8RtI9VNwJ2O3e2JZo6BSg=
----------------------EOF-----------------------

Seem to be quite a few untraceable files, does this mean they're not where they're supposed to be ?
 
No, but you are missing a couple of critical directories as I suspected.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Hi Softwaremaniac,

here they are

Code:
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-04-07 17:24:09.818
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Adr_isa\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs


Successfully created directory tree \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a.
Successfully created directory tree \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.966_none_1bd43d97ead19200.
Successfully created directory tree \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.966_none_94104941f1dbee45.
Successfully created directory tree \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.966_none_5f5c0b1a2d636400.


Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuauclt.exe to C:\WINDOWS\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuauclt.exe.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuaueng.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuaueng.dll.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wups2.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wups2.dll.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuuhosdeployment.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.15063.966_none_43e446db0ff7ef1a\wuuhosdeployment.dll.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.966_none_1bd43d97ead19200\usocore.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.15063.966_none_1bd43d97ead19200\usocore.dll.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.966_none_94104941f1dbee45\updatehandlers.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ratorupdatehandlers_31bf3856ad364e35_10.0.15063.966_none_94104941f1dbee45\updatehandlers.dll.
Successfully copied file C:\Users\Adr_isa\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.966_none_5f5c0b1a2d636400\dosvc.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.15063.966_none_5f5c0b1a2d636400\dosvc.dll.


Successfully restored ownership for C:\WINDOWS\winsxs
Successfully restored permissions on C:\WINDOWS\winsxs
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-04-07 17:24:20.616
Script hash: IJOuN9eVzcf6sMTWPZ1NHHBF9UXv1DAHnY17GRNbqy0=
----------------------EOF-----------------------

View attachment cbs.zip

Thanks, Adrian W.
 
Didn't take long to come up with the same error,

Code:
Setuperr.log

2018-04-07 18:00:56, Error                 CONX   0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

2018-04-07 18:01:37, Error                 IBSLIB BCD: Failed load key BCD00000000. Flags: 0x40 File: \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD Status: c000014c[gle=0x00000003]
2018-04-07 18:01:37, Error                 IBSLIB BCD: Failed to load hive into key BCD00000000 from \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD. Status: c000014c[gle=0x00000003]
2018-04-07 18:01:37, Error                 IBSLIB BCD: Failed to add system store from file. File: \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD Status: c000014c[gle=0x00000003]
2018-04-07 18:01:37, Error                 MOUPG  CDlpActionDiskSpaceReq::CalculateRequiredDiskSpaceInstallReq(1752): Result = 0x800703F1[gle=0x00000003]
2018-04-07 18:01:37, Error                 MOUPG  CDlpActionDiskSpaceReq::ExecuteInstallReq(1279): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CDlpActionDiskSpaceReq::ExecuteRoutine(501): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDiskSpaceAction> > > >::Execute(441): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CSetupManager::ExecuteTask(2170): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CSetupManager::ExecuteTask(2133): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CSetupManager::ExecuteInstallMode(715): Result = 0x800703F1
2018-04-07 18:01:37, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(347): Result = 0x800703F1
2018-04-07 18:01:39, Error                 MOUPG  CSetupManager::Execute(237): Result = 0x800703F1
2018-04-07 18:01:39, Error                 MOUPG  CSetupHost::Execute(375): Result = 0x800703F1

View attachment setupact.log

View attachment CBS.zip

We must be getting somewhere, I have the impression that the logs are getting smaller.

Best, Adrian W.
 
Make sure you have a complete backup of anything important on your computer BEFORE attempting any of these steps.

You will need a bootable Windows disc or recovery flash drive to boot from to do this.
How to create a recovery flash drive: https://support.microsoft.com/en-us/...recovery-drive

After you create the recovery drive, boot from it by using the advanced startup options and choosing boot from device (or using the UEFI interface, whichever is simpler :) ).
Here's the instructions that other users have had success with:



Alright, apparently the issue is with the BCD (Boot Configuration Data). A few users reported that rebuilding it solved that issue.

https://answers.microsoft.com/en-us/...4-9ae12cfd89a2 - "Most Helpful Reply" from Cifad

If you cannot read the commands properly, here goes (to be entered in the command prompt from the Recovery Environment):

diskpart - Opens the Disk Partitionning tool
select disk 0 - Will select your first hard drive (the one with the Windows partition on it)
list volume - Note the number of the partition that have no drive letter assigned to it, is of 260MB of size and have "FAT32" listed under the "FS" column
select volume X - X will be the number of your partition with a size of 260MB, the EFI System Partition one that you identified in the last command
assign letter=Z: - It'll assign the Z: letter to the EFI System Partition
exit - To exit the diskpart utility

Now you'll be back in the command prompt, enter the following commands:

cd /d Z:\EFI\Microsoft\Boot - Goes to the "Boot" directory in the Z: partition
attrib Z:\EFI\Microsoft\Boot\BCD -h -r -s - Removes the hidden, read-only and system attributes from the BCD folder
ren Z:\EFI\Microsoft\Boot\BCD BCD.old - Renamed the BCD folder to BCD.old
bootrec /rebuildbcd - This command will rebuild the BCD.

When it asks you Add the installation to boot list?, press on y followed by Enter and if it succeed, you'll have a The operation completed successfully message. Once you're done, close the command prompt, restart your computer and try to upgrade again.



Make sure you have a complete backup of anything important on your computer BEFORE attempting any of these steps.
 
Hi Softwaremaniac, when I try to create the recovery drive, I get this message ...

"We can't create a recovery drive on this PC. Some required files are missing. To troubleshoot problems when your PC can't start, use your Windows installation disc or media."

Can the same thing be done with a usb drive made from the media creation tool ?

Best, Adrian W.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top