bootmgr.exe errors in Microsoft's WIN 10 download

I have WIN 10 VERSION 14393.693. I wanted to do a clean install after all the upgrades from my RTM version so I went to MS downloads to get a copy. I used media creation tool to make a flash drive of the OS. When I open the smaller bootmanager file with Notepad I find the file is corrupted. The same thing happened when I downloaded a copy of my 8.1 pro as well. I used my Win 10 laptop to do both downloads. I used two different ISP's for the downloads to see if that made a difference.I checked my laptop with Malwarebytes and Defender to see if malware or a virus was causing the errors. I assume this is not safe to install from or is this something MS does until you activate the OS upon installation. The flash drives are 16GB drives. I am including the message copied from Notepad: ÿÿ  ÿ Boot Parameters size (0x%lx) is too big
BTAPENT =================== PAGE FAULT =================================

================== DOUBLE FAULT ================================

============== GENERAL PROTECTION FAULT ========================

===== STACK SEGMENT OVERRUN or NOT PRESENT FAULT ===============

===================== EXCEPTION ================================


DEBUG TRAP ** At linear address %lx

TRAP %lx
tr=%x cr0=%lx cr2=%lx cr3=%lx
gdt limit=%x base=%lx idt limit=%x base=%lx

cs:eip=%x:%lx ss:esp=%x:%lx errcode=%x
eax=%lx ebx=%lx ecx=%lx edx=%lx ds=%x es=%x
edi=%lx esi=%lx ebp=%lx cr0=%lx fs=%x gs=%x
flags=%lx Cy NoCy Zr NoZr IntEn IntDis Up Down TrapEn
TrapDis
Link %x
Esp0 %x
SS0 %x
Esp1 %lx
Cr3 %lx
Eip %lx
Eflg %lx
Eax %lx
Ebx %lx
Ecx %lx
Edx %lx
Esp %lx
Ebp %lx
Esi %lx
Edi %lx
ES %x
CS %x
SS %x
DS %x
FS %x
GS %x
Ldt %x
No physical memory is available at the location required for the Windows Boot
Manager. The system can not continue.
The Windows Boot Manager is incompatible with this system.
BOOTMGR image is corrupt. The system cannot boot. The file is possibly corrupt. The file header checksum does not match the computed checksum.
%lx
BMXHW_ `‰ MZ� ÿÿ ¸ @ à º ´ Í!¸LÍ!This program cannot be run in DOS mode.

$ rE”;+Ç;+Ç;+ÇVN.Æ5+ÇVN(Æ+ÇVN/Æ+ÇVN#Æm+ÇVN+Æ:+ÇVNÔÇ:+ÇVN)Æ:+ÇRich;+Ç PE L ��‰W à ! &» ¸ .rsrc ¸ @ @ ( � ä €4 V S _ V E R S I O N _ I N F O ½ïþ
98
98? Þ S t r i n g F i l e I n f o º 0 4 0 9 0 4 B 0 L C o m p a n y N a m e M i c r o s o f t C o r p o r a t i o n B
F i l e D e s c r i p t i o n B o o t M a n a g e r n ' F i l e V e r s i o n 1 0 . 0 . 1 4 3 9 3 . 0 ( r s 1 _ r e l e a s e . 1 6 0 7 1 5 - 1 6 1 6 ) 8 I n t e r n a l N a m e b o o t m g r . e x e € . L e g a l C o p y r i g h t © M i c r o s o f t C o r p o r a t i o n . A l l r i g h t s r e s e r v e d . @ O r i g i n a l F i l e n a m e b o o t m g r . e x e j % P r o d u c t N a m e M i c r o s o f t ® W i n d o w s ® O p e r a t i n g S y s t e m >
P r o d u c t V e r s i o n 1 0 . 0 . 1 4 3 9 3 . 0 D V a r F i l e I n f o $ T r a n s l a t i o n °

gcwizard said:

When I open the smaller bootmanager file with Notepad I find the file is corrupted.

Why are you doing that?

Originally opened trying to find which version of Win 10 was downloaded so I could record this. I always make a backup copy of the OS from Microsoft and then ID the flash drive somehow. I keep a record of these drives with descriptions of the contents of each. Noticed the bootmgr files are dated back at the RTM of 10.

Mount the ISO file. Mine gets drive letter J: when I mount it. Open command prompt (admin). Run:

dism /get-wiminfo /wimfile:J:\Sources\install.wim /index:1

Change the drive letter to what you get when you mount the ISO file. Also, if your ISO file has install.esd insead of install.wim, then use that for the file name. You should get a result like this:

Code:

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Details for image : J:\Sources\install.wim

Index : 1
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 14,747,431,455 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.14393
ServicePack Build : 0
ServicePack Level : 0
Edition : Professional
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 19070
Files : 103878
Created : 7/16/2016 - 7:05:47 AM
Modified : 7/16/2016 - 7:06:29 AM
Languages :
        en-US (Default)

The operation completed successfully.

Do index:2 instead of index:1 and you will find Home version.

It is not an iso. USB flash drive created with MS media creation tool. I tried the dism commands . Path not found message.

gcwizard said:

It is not an iso. USB flash drive created with MS media creation tool. I tried the dism commands . Path not found message.

If it is a dual 32 and 64 bit USB flash drive, then you will have to add \x86 or \x64 in front of \sources as in \x86\sources\install.wim or \x86\sources\install.esd. Also, change the drive letter to whatever drive letter your flash drive gets assigned.

Error 3 Path not found. I am very familiar with dism commands. I ran the commands every possible way, always leaving space before / but not before \.

gcwizard said:

Error 3 Path not found. I am very familiar with dism commands. I ran the commands every possible way, always leaving space before / but not before \.

Then it would seem like you do have a corrupt USB flash drive.

gcwizard: your initial post indicates you have arrived at the wrong conclusions:

"When I open the smaller bootmanager file with Notepad I find the file is corrupted. The same thing happened when I downloaded a copy of my 8.1 pro as well. I used my Win 10 laptop to do both downloads. I used two different ISP's for the downloads to see if that made a difference.I checked my laptop with Malwarebytes and Defender to see if malware or a virus was causing the errors. I assume this is not safe to install from or is this something MS does until you activate the OS upon installation. The flash drives are 16GB drives. I am including the message copied from Notepad:"

Bootmgr.exe has an "EXE" file extension, indicating that the file is an executable program - which is made up of compiled binary code that your Windows system can run, and some essential human readable text - which are generally error messages that the program displays when something goes wrong!
Hence the bits that you can read, (among the gibberish that Notepad displays when binary code that is not text is interpreted by the text editor as a string of characters), are lines that contain words like "FAULT", and that wonderful little clutch of error messages that panicked you:

"No physical memory is available at the location required for the Windows Boot
Manager. The system can not continue.
The Windows Boot Manager is incompatible with this system.
BOOTMGR image is corrupt. The system cannot boot. The file is possibly corrupt. The file header checksum does not match the computed checksum."

To put your mind at rest they are all perfectly normal for bootmgr.exe.

However, if you persist in opening executable files in text editors like Notepad, you may find that errors get saved back in those files, because Notepad may read a non-printing character as a different non-printing character, which would definitely corrupt the flow of the program.

If you need to find the Windows version of an executable file or dll, don't use Notepad, use File Explorer, right click on the file and look at the properties, and the details tab will give the information you need, e.g. this file which I picked at random:

I downloaded the official MS ISO of Win 10 last night. Mounted and checked the file using get-wiminfo command prompts. version 10.0.14393 x64 Home Languages en-US I used Hashcalc and the SHA1 value is: 18a044a4bb3341b0f4e2814241997deddfddef43 This does not match what I can find for the correct value but I may not have the current value. Is the correct number in the files somewhere? Thanks!