Win 10 update to 1067 fails with 0x80073BC3 error Anyone wanna Help me?

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


I don't see a fix. All I can show is an "orbit". A
series of things that may be related...

*******

https://answers.microsoft.com/en-us/...f-c65e69127d87

The requested system device cannot be found. (0x80073BC3)

[Maybe] VSS ASR Writer [Automated System Recovery]

*******

In an Administrator command prompt window.

vssadmin list writers

....

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {9c9a72d9-70f4-414d-88e2-9894fd7f13ca}
State: [1] Stable
Last error: No error --- check for error code

*******

Can also fail while doing a backup. If you have System Reserved
and C: , then System Reserved probably has the Active flag, and
Disk Management would list C: as "Boot" [which means System]
while the System Reserved would be "System" [which means boot].
The Active flag on an MBR disk, is set on the partition with the
boot folder, winload.exe, BCD file, and so on.

http://superuser.com/questions/26287...te-shadow-copy

So what the person there claims, is setting the Active flag helped.

You could probably do that from diskpart.

But then a question would be, how were you able to boot,
if this was broken ? If there are multiple disk drives, the
System Reserved might actually be on another disk. In a GUID-based
OS this isn't supposed to matter. However, the VSS system (on a desktop)
isn't allowed to span multiple disks - the shadow copy must stay on the
drive it came from. Only a server allows redirection of shadows.

*******

Associated with this, is the Recovery partition (450MB). Rene wasn't
able to make emergency boot media, and I found my Recovery partition
wasn't set up properly. Could the ASR Writer fail if this wasn't
set up ? Dunno.

http://al.howardknight.net/msgid.cgi...nt-email.me%3E

http://al.howardknight.net/msgid.cgi...nt-email.me%3E

Paul

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


I'd probably start with the output of Disk Management
as well as an Administrator command prompt where you'd run

cd %userprofile%\Downloads

bcdedit output.txt

If any of the bdedit fields are undefined, that is a start.
The other aspects will become more clear when you look at
Disk Management (while the still-operational OS is booted),
and note what is missing or out-of-the-ordinary.

While the Windows 10 installer will "add" a partition
in some cases on install, it isn't exactly a paragon of
virtue in terms of setting everything up properly. That's
why I had to do the reagentc recipe on my setup, to get
part of it working. Generally, my installs have always
worked, but some of the cosmetic details have not been
100% correct.

And several times now, I've had to use the Windows Update
troubleshooter, to "get Windows Update out of a hole".
Windows Update continues to be a "pile of crap" for Microsoft.

Paul

On Tue, 28 Feb 2017 01:35:35 -0500, Paul
wrote:

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


saw your other reply and will delve deeper into it a little later.
when my machine is not being used so much.


I'd probably start with the output of Disk Management
as well as an Administrator command prompt where you'd run

cd %userprofile%\Downloads

bcdedit output.txt

If any of the bdedit fields are undefined, that is a start.
The other aspects will become more clear when you look at

took a look and nothing seems out of place. Nothing undefined.

Disk Management (while the still-operational OS is booted),
and note what is missing or out-of-the-ordinary.

again .... nothing unusual in the disk management.
the only thing that might be considered odd is that I do no have a
system recovery partition on the boot drive. single partition for the
whole drive.

While the Windows 10 installer will "add" a partition
in some cases on install, it isn't exactly a paragon of
virtue in terms of setting everything up properly. That's
why I had to do the reagentc recipe on my setup, to get
part of it working.

will look into that a little later.

Generally, my installs have always
worked, but some of the cosmetic details have not been
100% correct.

And several times now, I've had to use the Windows Update
troubleshooter, to "get Windows Update out of a hole".

trouble shooter has been run several times now and the only thing it
can't seem to correct as it is there every time I run it is it won/t
sense the proxy settings...... I have no proxy set up at all.

Windows Update continues to be a "pile of crap" for Microsoft.

cant argue that.......

Paul
thanks for your help.
kallita

On Mon, 27 Feb 2017 21:13:53 -0500, Paul
wrote:

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


I don't see a fix. All I can show is an "orbit". A
series of things that may be related...

*******

I too have been finding nothing definitive..... which is why I came
for help.


https://answers.microsoft.com/en-us/...f-c65e69127d87

The requested system device cannot be found. (0x80073BC3)

[Maybe] VSS ASR Writer [Automated System Recovery]

*******

In an Administrator command prompt window.

vssadmin list writers


group policy is blocking command.......

...

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {9c9a72d9-70f4-414d-88e2-9894fd7f13ca}
State: [1] Stable
Last error: No error --- check for error code

*******

Can also fail while doing a backup. If you have System Reserved
and C: , then System Reserved probably has the Active flag, and
Disk Management would list C: as "Boot" [which means System]
while the System Reserved would be "System" [which means boot].
The Active flag on an MBR disk, is set on the partition with the
boot folder, winload.exe, BCD file, and so on.


There is no system reserved partition on the boot/windows drive .
Single partition with windows only


http://superuser.com/questions/26287...te-shadow-copy

So what the person there claims, is setting the Active flag helped.

You could probably do that from diskpart.

But then a question would be, how were you able to boot,
if this was broken ? If there are multiple disk drives, the
System Reserved might actually be on another disk. In a GUID-based
OS this isn't supposed to matter. However, the VSS system (on a desktop)
isn't allowed to span multiple disks - the shadow copy must stay on the
drive it came from. Only a server allows redirection of shadows.

*******




Associated with this, is the Recovery partition (450MB). Rene wasn't
able to make emergency boot media, and I found my Recovery partition
wasn't set up properly. Could the ASR Writer fail if this wasn't
set up ? Dunno.


You would think that the install program would set up or at least
check for the needed partitions during the install....... but then we
are dealing with Microsoft here......


http://al.howardknight.net/msgid.cgi...nt-email.me%3E

http://al.howardknight.net/msgid.cgi...nt-email.me%3E

Paul

kallita

On 2017-02-28, james moffat wrote:


I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita

I have similar issue because of unregistered office. When I removed
office update went smoothly...

--
press any key to continue or any other to quit...

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


Here's another comment on ASR.

https://www.storagecraft.com/support...ailed-status-8

"The ASR writer stores the configuration of disks on the system.
This writer reports the Boot Configuration Database (BCD) and
is also responsible for dismounting the registry hive that
represents the BCD during shadow copy creation."

(KB 32 refers to this article, not particularly interesting...

http://www.storagecraft.com/support/kb/article/32 )

Another possibility, is your comment with regard to "vss list writers".
You said a Group Policy was blocking that. If you opened an
Administrator command prompt window (by right-clicking Start
and looking in the menu), it should have been possible to run
that command. Maybe the ASR is failing, because basically, all
of VSS is busted at the moment ? Maybe you have trouble running
any free (VSS based) backup tools too ? Macrium Reflect Free
uses VSS for example. Acronis should too.

To see what Group Policies are in effect, you can try this:

1) Open an Administrator Command Prompt.

2) cd %userprofile%
cd Downloads
gpresult /H GPReport.html
firefox GPReport.html --- or go to your Downloads folder and
double-click the HTML file and open it
in a browser that way.

That should work on Win10 Pro, which should have a complete and
working Group Policy installation. Any "deltas" from system defaults,
should be listed in the HTML report, so the list of exceptions
should be quite short. Only an IT guy who spends all day turning
that stuff on, should have an extensive list. My installs here
might have zero or one of those, so the list would be quite short.

I don't see a point in running SFC or using DISM repairhealth,
because in this case, it looks like an active subsystem is
not working properly. Rather than the collection of files itself
being defective.

Paul

On Tue, 28 Feb 2017 21:54:07 +0000 (UTC), Melzzzzz
wrote:

On 2017-02-28, james moffat wrote:


I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita

I have similar issue because of unregistered office. When I removed
office update went smoothly...

thanks for the info.
I have a copy of office 10 fully registered on my system . and will
check into that later
kallita

On Tue, 28 Feb 2017 20:14:59 -0500, Paul
wrote:

james moffat wrote:

I am attempting to update my windows 10 pro to the latest 1067
anniversary update, but it is constantly failing at the safe_os phase
error during preparerollback spot with error 0x80073BC3-0x20009.
so far i have attempted several times to do it through the windows
update function in windows, several times tried with the windows 10
upgrade assistant, and have removed all drives except the os drive
from my system. I have even tried running the upgrade iso from USB for
both repair and install, but it stops at that point no matter what i
do.
the OS is on an ssd drive if that makes any difference.
Is anyone willing to help out in getting this update to work for me?
Any suggestions would be appreciated.
thanks for your time
kallita


Here's another comment on ASR.

https://www.storagecraft.com/support...ailed-status-8

"The ASR writer stores the configuration of disks on the system.
This writer reports the Boot Configuration Database (BCD) and
is also responsible for dismounting the registry hive that
represents the BCD during shadow copy creation."

(KB 32 refers to this article, not particularly interesting...

http://www.storagecraft.com/support/kb/article/32 )

Another possibility, is your comment with regard to "vss list writers".
You said a Group Policy was blocking that. If you opened an
Administrator command prompt window (by right-clicking Start
and looking in the menu), it should have been possible to run
that command. Maybe the ASR is failing, because basically, all
of VSS is busted at the moment ? Maybe you have trouble running
any free (VSS based) backup tools too ? Macrium Reflect Free
uses VSS for example. Acronis should too.

To see what Group Policies are in effect, you can try this:

1) Open an Administrator Command Prompt.

2) cd %userprofile%
cd Downloads
gpresult /H GPReport.html
firefox GPReport.html --- or go to your Downloads folder and
double-click the HTML file and open it
in a browser that way.

That should work on Win10 Pro, which should have a complete and
working Group Policy installation. Any "deltas" from system defaults,
should be listed in the HTML report, so the list of exceptions
should be quite short. Only an IT guy who spends all day turning
that stuff on, should have an extensive list. My installs here
might have zero or one of those, so the list would be quite short.

I don't see a point in running SFC or using DISM repairhealth,
because in this case, it looks like an active subsystem is
not working properly. Rather than the collection of files itself
being defective.

Paul

Nothing unusual showed up in the group policies......
For me that was just another bunch of unexplained weirdness that shows
up in windows.

anyway's.... I finally got windows feature 1067 installed.
The procedure was not something I found but just trial and error until
windows finally gave up and said....If you want it this bad I will
give it to you.

after a couple more tries running troubleshooters and boot repairs and
not getting anywhere I finally did this:

Took the ssd drive out completely and dropped in an old windows 7
laptop drive to test to make sure the install USB was not the problem
, and the install went without a hitch.

while I was running the updated laptop drive I connected the ssd and
opened up diskmanager and added a unallocated 1gb partition to the
ssd. This is what I think actually made the difference.

Then shut down and pulled the laptop drive out booted into windows
from the ssd and ran the update from the USB once again. The install
went fine this time , with no errors showing up.
If I were to give a final solution to this error I would have to say
that the Boot drive requires Some sort of partition to put the system
reserved partition into for it to work. And for some reason was unable
to create one on my ssd even though it had plenty of room to do so.
So ass it stands I now have a seemingly functioning version 1067 of
windows on my machine.
thanks to all for your advice and suggestions
kallita