updated fail

Thanks for the log files.

The evaluation confirms my assumption that the boot files should be updated.
000003df (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll ErrorCode: 80070070 Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]

Error code 80070070 means ERROR_DISK_FULL - There is not enough space on the disk.

You need to create free space on the system reserved partition.

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)

If that doesn't work, we'll have to try a other way.

I would not get back to you today due to the time difference.


Friendly greetings

When using google make sure that they are available without sign in.

zbook said:

When available please post share links for results: (one drive, drop box, or google drive)


[FONT="]Tuneup.bat[/FONT][FONT="] - Click here to go to the BSOD batch repository to download and run this batch file.[/FONT]


LOGS.bat[FONT="] - Click here to go to the BSOD batch repository to download and run this batch file.[/FONT]


[FONT="]V2 and DM:[/FONT]
BSOD - Posting Instructions


[FONT="]Windows update troubleshooter:[/FONT]
Troubleshoot Problems in Windows 10 with Troubleshooters



For any problems running the log collectors > post images of error messages and codes

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

tuneup
tuneup.txt - Google Drive

Logs
LOGS.zip - Google Drive

- - - Updated - - -

macstl said:

tuneup
tuneup.txt - Google Drive

Logs
LOGS.zip - Google Drive

Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -

zbook said:

When using google make sure that they are available without sign in.

Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -

dalchina said:

Again from post #5 please..

How much free space do you have on C: ?
Post a screenshot of your partitions using a 3rd party (free) partition manager - not Disk Management - like this:
Attachment 310854


Given your setuperr.log, from an admin command prompt run
reagentc /info
and post a screenshot of the result.

Your previous screenshot says you only have 2 partitions. Do you believe you have a UEFI or a MBR based installation? It would seem it must be MBR - is that correct?

Basics: please check your disk- it's an older laptop and disk.
E.g. Hard Disk Sentinel (trial) - there's a portable version- best instant comment.
Else just SMART params- Crystal Diskinfo (free).

Then from an admin command prompt run
chkdsk c: /scan

If ok use this:
Reset Windows Update in Windows 10

Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -

Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

macstl said:

tuneup
tuneup.txt - Google Drive

Logs
LOGS.zip - Google Drive

- - - Updated - - -



Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -



Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -



Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

- - - Updated - - -

Problem solved by Tekkie Boy. He found a not enough disk space error in /CBS folder and directed me to

Please try the section "Windows 10 with MBR partition" from there:
“We couldn’t update system reserved partition” error installing Windows 10 (microsoft.com)
This procedure enabled me to fully install the upgrade that failed.
Thank you for all your efforts!

Hello my first post here on the forum.

the Problem is the EFI partition wich is to small for the Win10upgrade to the new version.
It happends a lot with HP laptop and their image installation.
You have to expand the EFI partition wich is not so easy but makeable.

As an administrator you can open the CMD and use "diskpart" and "AOMEI Partition Assitent". After that you have to asssign a drive letter to EFI partition and expand the partition to 350 MB.

# use the letter/number wich is showed as
-> Hit ENTER

open CMD console as administrator ->
diskpart ->
list disk ->
select disk # -> mostly disk 0(zero) ( example = select disk 0 )
list vol -> to show the volumens on disk 0, choose the volume number with the Fat32 it has a 100MB space used
select vol # -> the volumen nummber ( example = select vol 3 )
assign letter = # -> use a letter wich is free to assign( example = assign letter = J )

when the drive letter is assigned you can go ahead with AOME partition assitent to expand the drive letter wich we have assigned with disk part. YOu need a Fat32 drive with at least 250 MB shown to expand the EFI partition.
AOME partition assitentt will boot int DOS so it can allocat the newly setten drive space.

After that windows 10 updates will be install, that was my solution for this

SilversurferMVP said:

the Problem is the EFI partition

In this thread the OP has BIOS Legacy and disk MBR.
There is no EFI partition.

zbook said:

Please post the steps that you used.

(commands with results)


When available post results for:

[FONT="]V2 and DM:[/FONT]
BSOD - Posting Instructions

what is V2 and DM?

- - - Updated - - -

zbook said:

Please post the steps that you used.

(commands with results)


When available post results for:

[FONT="]V2 and DM:[/FONT]
BSOD - Posting Instructions

at this link I used the steps listed under the "windows with MBR" selection
https://support.microsoft.com/en-us/...alling-windows

I don't want to go through the whole thing again to get a cmd screen to copy.

V2 is the log collector used in our BSOD forum:
BSOD - Posting Instructions

Please upload results into this thread:
How to Upload and Post Screenshots and Files at Ten Forums

The prior logs indicated possible drive problems.
There should be additional information in these logs.

zbook said:

V2 is the log collector used in our BSOD forum:
BSOD - Posting Instructions

Please upload results into this thread:
How to Upload and Post Screenshots and Files at Ten Forums

The prior logs indicated possible drive problems.
There should be additional information in these logs.

I pressed the shortcue after opening V2 and got this:

Code:

& : The term '.\resources\main.ps1' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:2
+ &'.\resources\main.ps1'
+  ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (.\resources\main.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Windows\System32>

Make sure extract all is clicked.

List any non-Microsoft software:
antivirus
firewall
drive encryption