recovery environment 0xc000000f code


Author
Message
Nick
Nick
Macrium Representative
Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)Macrium Representative (4.9K reputation)
Group: Administrators
Posts: 3K, Visits: 17K
Thanks for posting.

For those that  have been seeing an error when starting the rescue environment from the boot menu, can you try disabling Windows 'Fast Start' to see if that resolves the problem?. The Windows boot menu can be rendered inoperable if updated during a Windows 'Fast Start' boot sequence. 

https://www.windowscentral.com/how-disable-windows-10-fast-startup?amp


Kind Regards

Nick - Macrium Support



Edited 12 February 2020 7:06 PM by Nick
dbminter
dbminter
Most Valuable Professional
Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)
Group: Forum Members
Posts: 3.3K, Visits: 31K
Frank Esposito - 12 February 2020 6:31 PM
dbminter - 12 February 2020 6:19 PM
For what it's worth, I updated to the latest Reflect version and the boot menu option works fine for me.  I have an SSD and am running Windows 10 1909 (18363.657).  Just updated yesterday to the latest Patch Tuesday patch version.

Umm ... it seems like the "657" build worked --- I do a win update to confirm


So, you hadn't yet applied yesterday's Patch Tuesday's update?


It is somewhat worrying that it could be the cause.  That people without the latest Windows 10 patch might not be able to get the boot menu recovery to start.

L. W. "Dan" Danz
L. W. "Dan" Danz
Expert
Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)
Group: Forum Members
Posts: 471, Visits: 5.2K
Unfortunately I have to revise my findings (that it worked for me).  On a second computer system, I installed KB4532693 Cumulative Update for Win10 1909 among others (it's the most likely culprit, then installed 4711.  This worked okay .. i.e. the MR boot menu worked okay.  So I experimented a bit.  I have been building with the Copy USB drivers switch turned on.  So I turned it off, forced a rebuild of the boot menu, and rebooted to Windows.  But when I then rebooted to MR's boot menu, I got the error that others have seen.   

So, I booted back into windows, turn on the Copy USB drivers switch, forced a rebuilt of the boot menu, and rebooted to Windows.  When I rebooted to MR's boot menu, THE ERROR CONTINUED TO SHOW UP. 

I booted from an earlier recovery flash drive,  reloaded the C: (system) drive from a backup (which removed all of today's window updates including KB4532693), but I deliberately did not reload the D: (data) drive. NOTE The \boot\Macrium files are on the D: drive.  When I rebooted after the reload, windows loaded okay, and so did WinRE 1903 with the 4711 files in it (I had not re-updated MR on windows, it was still 4601).  Strange. 

I just saw
@nick post about Fast Startup -- I have it enabled on both of these computers, and will report results.



@Nick I turned off fast startup for the following.
Restart.   Windows update ran and reinstalled all the updates, including KB4532693).  Restart to finish installing updates.
Force rebuild of the recovery 1903 wim (yes, 1903 even tho I'm on 1909 - that's nothing new).
Windows reboots okay,  Recovery does NOT work (same error), acts like possibly it can't find the D: drive with the /boot/Macrium area.
Uninstalled KB4532693.  So I'm back to 18363.592.
I'm rebooting into windows and will try to rebuild the boot menu.
If that doesn't fix it, I will move the /boot/macrium files to the C: drive and rebuild.




 L W "Dan" Danz, Overland Park KS 
MR v8.0.6392+ Win10.21H2-19044.1415+ & Win11.21H2-22000.474+




Edited 12 February 2020 9:46 PM by L. W. "Dan" Danz
L. W. "Dan" Danz
L. W. "Dan" Danz
Expert
Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)
Group: Forum Members
Posts: 471, Visits: 5.2K
Okay, I found another bug ...
Create Rescue Media ... Advanced....Rescue Media Volume...
Each time you change from C: to D: or vice versa   the files are copied from old location to the new location, except it does it by e.g. copying C:boot\macrium to D:\boot\macrium -- so it extends the directory to D:\boot\macrium\macrium  and next time from D: back to C:becomes C:\bootmacrium\macrium\macrium.  This is not the original problem of this post, so I will open another, with logs.   But right now, I can't test changing the rescue media volume. 

Sigh. 


 L W "Dan" Danz, Overland Park KS 
MR v8.0.6392+ Win10.21H2-19044.1415+ & Win11.21H2-22000.474+




Frank Esposito
Frank Esposito
Proficient Member
Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)
Group: Forum Members
Posts: 243, Visits: 625
Hello -- I just finished all the update for day which includes KB4532693 --- in  addition I also TURN OFF  "fast startup" . 

The reflect boot recovery still  fails with the same status code as before
L. W. "Dan" Danz
L. W. "Dan" Danz
Expert
Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)Expert (990 reputation)
Group: Forum Members
Posts: 471, Visits: 5.2K

Recap and updated status:

As I first posted, my first system, which had today's Win10 updates applied, and then MR updated from 4601 to 4711, and then 4711 added to the WinRE recovery code, worked without errors.

On the second system, I encountered the OP's original problem when I tried to turn off Copy USB drivers, forcing a complete rebuild of the WinRE wim.   I never could do a successful rebuild of the WinRE wim with setting or resetting the Copy USB drivers switch.    Matters got worse when I tried to switch the location of Macrium media from D: to C:

I gave up and I restored both c: and d: drives so that my second system status is:
Rescue Media Volume is where it was originally, on D: (to save space on C: which is an SSD). I will not try to move it back to C: because of the problem with cascading Macrium subdirs in \boot.
The original restore of C: re-established MR 4601, and build 18363.592.  Today's updates, including KB4532693, have been applied.
OS Build Info shows: version 1909 -  18363.657
After the update of the OS, MR was updated to 7.2.4711.  I was careful with Create Rescue Media operations so that the WIM was NOT rebuilt from scratch at any time.  After MR 7.2.4601 was updated to 7.2.4711, the version of MR in the boot menu area was updated, but this did NOT rebuild the entire boot menu.
And the recovery option from the windows boot manager menu successfully loads MR 7.2.4711.

I'm going to hold on MR updates at this point, or if I do apply an update and have to rebuild the boot menu, I will very carefully do it and take snapshot backups before/after.
I believe there is a problem in the rescue builder code that led to the original problem, and I cannot say whether the problem involves KB4532693 or not.  There is also a bug in the Rescue Builder that causes the cascading \boot\macrium sub-directory problem if the media volume is changed.  So my advice to anyone else is DO NOT CHANGE THE MEDIA VOLUME SELECTION until this is resolved.  Unfortunately I did not save the any of the rescue builder log files before restoring from backup (my bad). But developers should be able to reproduce that issue.  My running/working BCD has this for the Recovery section:
Windows Boot Loader
-------------------
identifier     {3913c9eb-f338-11e8-bf8e-000272a7bd8d}
device      ramdisk=[D:]\boot\macrium\WinREFiles\media\sources\boot.wim,{ramdiskoptions}
path       \windows\system32\boot\winload.efi
description     Macrium Reflect System Recovery
osdevice      ramdisk=[D:]\boot\macrium\WinREFiles\media\sources\boot.wim,{ramdiskoptions}
systemroot     \Windows
nx        OptIn
detecthal     Yes
winpe       Yes

When it was bad because of the cascading directory problem (after a few retries going back and forth),  it ended up with many \macrium repetitions and a double \\ in front of WinREFiles. so it looked like this for both the device and osdevice entries:
ramdisk=[D:]\boot\macrium\macrium\macrium\macrium\macrium\macrium\\WinREFiles\media\sources\boot.wim,{ramdiskoptions}
I strongly suspect this ramdisk is the "device" that the loader cannot find when trying to load the files for the recovery boot.

@Nick: I cannot, with certainty, say whether turning off Fast Startup helped or not. It's currently "off" for the second system (a server which seldom boots), and has never been "off"  for the first system (laptop, which boots a lot).  Could you give a bit more information about how it mucks things up when "on"?

I wonder if @dbminter or @fpefpe rebuilt the whole WinRE boot menu when doing the updates to MR



 L W "Dan" Danz, Overland Park KS 
MR v8.0.6392+ Win10.21H2-19044.1415+ & Win11.21H2-22000.474+




Frank Esposito
Frank Esposito
Proficient Member
Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)
Group: Forum Members
Posts: 243, Visits: 625
Hello --  I never got into "the weeds" on  rebuilding the   recovery boot -- I just  take the defaults -- 

I first discovered the issue when I did a rebuild from PE 3.1 to PE 10 -- 
dbminter
dbminter
Most Valuable Professional
Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)Most Valuable Professional (4.8K reputation)
Group: Forum Members
Posts: 3.3K, Visits: 31K
Well, I don't know if it rebuilds whatever it was Smile I just selected to update the boot menu recovery environment to match the new version of Reflect.  Every time I update Reflect to a new version, I update the boot menu recovery environment.

JasonUK
JasonUK
New Member
New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)New Member (18 reputation)
Group: Forum Members
Posts: 13, Visits: 99
Frank Esposito - 12 February 2020 11:22 PM
Hello -- I just finished all the update for day which includes KB4532693 --- in  addition I also TURN OFF  "fast startup" . 

The reflect boot recovery still  fails with the same status code as before

Same here.  Fast start was enabled and as I've never set same it must have been by default.  Applied all Windows updates so I've now got WIndows 10 / 1909 / OS Build 18363.657.  Ran a full image backup, switched off fast start and rebooted before I tried updating Reflect again...

Updated Reflect, updated boot menu, net result identical failure to OP - fails to load Reflect environment when selected from boot menu.  Loading Reflect environment from external media (CD or USB flash drive) worked without issue.

Recovered system from the image created back to Reflect 7.2.4601 and all works fine again.
Edited 13 February 2020 9:46 AM by JasonUK
Frank Esposito
Frank Esposito
Proficient Member
Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)Proficient Member (342 reputation)
Group: Forum Members
Posts: 243, Visits: 625
Nick - 12 February 2020 6:43 PM
Thanks for posting.

For those that  have been seeing an error when starting the rescue environment from the boot menu, can you try disabling Windows 'Fast Start' to see if that resolves the problem?. The Windows boot menu can be rendered inoperable if updated during a Windows 'Fast Start' boot sequence. 

https://www.windowscentral.com/how-disable-windows-10-fast-startup?amp

Hello --- Anything new to report on this issue?  --- turning off "fast start" did not correct the issue  -- 
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search