Jump to content

Need Help! Modify bootmgr windows 8


congnt92

Recommended Posts

  • 1 month later...

  • 2 months later...

So for everyone how doesn't like command line or hex editing, I've updated my old zbootmgr tool.

 

http://1drv.ms/1plzVcu

 

Thanks for sharing :)

But I don't know why running this tool for modity bootmgr windows 8.1, I get "Unsupported OS, newer ntdll.dll needed!" error

 

 

Here you have the addresses for bootmgr.exe version 6.3.9600.16384 (RTM)

0000065E: 0F 90

0000065F: 88 90

00000660: AE 90

00000661: 02 90

00000662: 00 90

00000663: 00 90

0002B1C1: 74 EB

0002B1EB: 75 EB          At address 8AF90 you have the \Boot\BCD string that you can change.

 

With bootmgr windows 8.1 update (6.3.9600.16415). At address 0000065E: is 01 not 0F. Can I change it to 90 ?

And now, Windows 10 was came. I can't modify bootmgr windows 10 by this way.

Can you update the method to modify bootmgr windows 8.1 update and bootmgr windows 10?

Thanks

Edited by congnt92
Link to comment
Share on other sites

"Unsupported OS, newer ntdll.dll needed!"

 
Means your running this tool not under Windows 8, and your ntdll.dll has not the functions to decompress and recompress bootmgr.
You can put ntdll.dll from a win8 install next to the program an try again.
 
If the offset has changed, then please don't change these bytes.
If I have some time I take  a look at the new version.
But seriously you don't need a win10 bootmgr, do you?
Link to comment
Share on other sites

 

"Unsupported OS, newer ntdll.dll needed!"

 
Means your running this tool not under Windows 8, and your ntdll.dll has not the functions to decompress and recompress bootmgr.
You can put ntdll.dll from a win8 install next to the program an try again.

 

 

I run this tool under windows 8.1 spring update. Version Bootmgr in windows 8.1 spring update is 6.3.9600.16415 not 6.3.9600.16384. May this is reason why i get that error.

 

 

If the offset has changed, then please don't change these bytes.

 

As you say, in ver 6.3.9600.16415, We only need to change \Boot\BCD to custom value. What about these

 

0000065E: 0F 90

0000065F: 88 90

00000660: AE 90

00000661: 02 90

00000662: 00 90

00000663: 00 90

0002B1C1: 74 EB

0002B1EB: 75 EB

 

 

Thanks

Link to comment
Share on other sites

congnt92, please re-download and try again.

 

http://1drv.ms/1plzVcu

 

Thanks. I run it under windows 8.1 update 1 and windows 10 technical preview. It work fine on windows 8.1 update 1. It does not support for win 10.

And I still have a question.

- If we modify bootmgr manally (decompress, hex edit, checksum, recompress), the size of bootmgr (after modified) less original bootmgr about 3kb.

- If using your tool, bootmgr after modified is same size with original bootmgr.

Could you tell me why?

And it would be greater if your tool allow user create modified bootmgr with "ABC" string instead "BC0, BC1, ..." :D

And your tool work fine but I want to learn how to manually modified bootmgr as you guide me at #3 (decompress, hex edit, recompress ...). Can you guide me?

And thanks again, JFX.

Edited by congnt92
Link to comment
Share on other sites

Yeah, better let's wait for Win10 final  ;)

 

Well, bmzip.exe does compress better, so the new bootmgr will be slighlty smaller.

I use the same compression code MS uses, so the size will stay more or less equal.

 
Maybe next year I'll add "ABC" feature.

 

This should be the offsets for 6.3.9600.16415

0000CF0E: 0F 900000CF0F: 88 900000CF10: AE 900000CF11: 02 900000CF12: 00 900000CF13: 00 90000194A9: 74 EB000194D3: 75 EB          At address D84 you have the \Boot\BCD string that you can change.
Link to comment
Share on other sites

 

Yeah, better let's wait for Win10 final  ;)

 

Well, bmzip.exe does compress better, so the new bootmgr will be slighlty smaller.

I use the same compression code MS uses, so the size will stay more or less equal.

 

Maybe next year I'll add "ABC" feature.

 

This should be the offsets for 6.3.9600.16415

0000CF0E: 0F 900000CF0F: 88 900000CF10: AE 900000CF11: 02 900000CF12: 00 900000CF13: 00 90000194A9: 74 EB000194D3: 75 EB          At address D84 you have the \Boot\BCD string that you can change.

Wow. Can you tell me how to calculate the offsets to change value?

Link to comment
Share on other sites

Are you sure that delay comes from bootmgr?

It boots instantly for me!

 

I'm sure. Because if I use bootmgr original, no matter what happend. You can send me your bootmgr file after modified?

 

 

I'm sorry. The reason why I get delay issue is resources folder was missing on my usb.

I created a multi installing windows usb. So some unnecessary folder was removed: support, fonts, en-us, ... (include resourecs folder in boot folder). resources folder contain bootres.dll and because it was removed from my usb so i got delay issue.

 

So now, if I can, I want to ask

"How can I keep bootres.dll file same a USB which contain 2 sources of windows 7 and 8 ?". I guess that bootres.dll is load by boot.wim or BCD or something. Such as, if bootres.dll is loaded by Boot.wim, so I want to Boot.wim of windows 7 load bootre1.dll (to solve delay issue windows 7 installing), Boot.wim of windows 8 load bootre2.dll (to solve delay issue win 8 installing).

 

Of coures, missing bootres.dll file will make delay issue, but this error is not affect to the installing windows. Just, It could be better if we can resolved.

Thanks :)

Edited by congnt92
Link to comment
Share on other sites

  • 10 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...