fyi  -- It has been reported that KB4532693 and KB4524244 could cause issues with boot managers --- 

https://www.techradar.com/news/the-latest-windows-10-updates-are-causing-more-serious-issues

+x

 

Frank Esposito - 14 February 2020 4:29 PM

fyi  -- It has been reported that KB4532693 and KB4524244 could cause issues with boot managers --- 

https://www.techradar.com/news/the-latest-windows-10-updates-are-causing-more-serious-issues

Thanks everyone for posting on this problem.

We've discovered that RMBuilder.exe v7.2.4711 can create a BCD entry with an invalid path syntax which causes the 0xc000000f error. This occurs if the PE version is changed and the boot menu is re-built, or if built from scratch. This explains why the problem hasn't been seen by all. 

We'll have an update available as soon as we've confirmed the fix. Apologies for the inconvenience this has caused.

Kind Regards

Nick

Macrium Support

See our reviews on

+x

 

Nick - 14 February 2020 4:40 PM

+x

 

Frank Esposito - 14 February 2020 4:29 PM

fyi  -- It has been reported that KB4532693 and KB4524244 could cause issues with boot managers --- 

https://www.techradar.com/news/the-latest-windows-10-updates-are-causing-more-serious-issues

Thanks everyone for posting on this problem.

We've discovered that RMBuilder.exe v7.2.4711 can create a BCD entry with an invalid path syntax which causes the 0xc000000f error. This occurs if the PE version is changed and the boot menu is re-built, or if built from scratch. This explains why the problem hasn't been seen by all. 

We'll have an update available as soon as we've confirmed the fix. Apologies for the inconvenience this has caused.

Good news.   Thanks for jumping in, @Nick .... will the fix also address the problem of cascaded /macrium subdirectories in c:/boot if a user changes the volume used for the recovery data?   Also, are you still suspecting involvement of Fast Startup?

+x

 

L. W. "Dan" Danz - 14 February 2020 4:48 PM

+x

 

Nick - 14 February 2020 4:40 PM

+x

 

Frank Esposito - 14 February 2020 4:29 PM

fyi  -- It has been reported that KB4532693 and KB4524244 could cause issues with boot managers --- 

https://www.techradar.com/news/the-latest-windows-10-updates-are-causing-more-serious-issues

Thanks everyone for posting on this problem.

We've discovered that RMBuilder.exe v7.2.4711 can create a BCD entry with an invalid path syntax which causes the 0xc000000f error. This occurs if the PE version is changed and the boot menu is re-built, or if built from scratch. This explains why the problem hasn't been seen by all. 

We'll have an update available as soon as we've confirmed the fix. Apologies for the inconvenience this has caused.

Good news.   Thanks for jumping in, @Nick .... will the fix also address the problem of cascaded /macrium subdirectories in c:/boot if a user changes the volume used for the recovery data?   Also, are you still suspecting involvement of Fast Startup?

Hi Dan

The creation of the cascading sub directories has been fixed. If detected, the existing folders will be deleted and correct folder structure will be re-created under '\boot'.

Fast Startup is a red herring in this instance but it has been known not to play well with BCD entries in the past. 

Again, apologies for the for the inconvenience this has caused. 

Kind Regards

Nick

Macrium Support

See our reviews on

Hi,

Sorry to "re-open" an old thread but I just updated MRH to v8.0.6979 [UEFI]. The update ran AOK & I went through the normal process of updating the MRH Rescue Media ... both Windows Boot Menu & USB.

I didn't notice any issues doing so, except that MRH said that I was using the 32bit version of Windows 10 RE & the update changed this to the 64bit version of Windows 10 RE. I previously never knowing selected either the 32bit or 64bit version of Win10 RE, ie. I let MRH choose the appropriate version for my PC.

When I rebooted my PC to select the MRH Recovery from the Windows Boot Menu it failed with:

Status: 0xc000000f
Info: A required device isn't connect or cant be accessed.

(I did take a screen shot but it's the same as previously posted in this thread.)

I've NOT experience any issue with MRH Recovery in any previous versions of MRH (all the way back to v4 or v5 of MR).

I then booted from my MR USB drive that I just updated & MRH Recovery ran just fine. In the title line it says: MR Home v8.0.6979 Windows 10 RE Version 2004 (64Bit) [UEFI]

I then tried to recreate & go back to the 32bit version of Windows 10 RE in the MRH Boot Menu but MRH wouldn't let me change it back.

* So how do I fix this problem?
* How do I go back to the previous version of MRH?
(I've been really slack & I don't have a recent PC backup to revert to an older version of MRH by restoring my PC. In hindsight I wish I did a backup of my PC BEFORE upgrading MRH.)

I'm running the latest version of Win 10 Pro 64Bit (including the monthly updates).
The PC is rather old ... built back in December 2014./January 2015.

Cheers
BazzaG...

Edit ... Oops this is for the wrong version of MRH. I'll create a new post. Sorry.