Posts: 56
Threads: 7
Joined: Dec 2023
Reputation:
0
Here's an odd issue. It's not a bug, but something quirky. There seems to be a difference in PE/RE builds. When you use the option to add HBS to the boot menu it creates a c:\boot option, just like pretty much every other imaging apps. However, when you initiate a restore within Windows it creates an .iso and uses that as a temporary PE. My question is, why? Why not use the same PE instance that the boot entry uses? It seems needlessly redundant to use two variation of the same PE.
Posts: 56
Threads: 7
Joined: Dec 2023
Reputation:
0
Because they don't. Every time I try to restore an image within Windows, thus forcing it to reboot, HBS creates an .iso and uses that. If I delete that file I get prompted that I need to create the iso. The timestamp on that .iso is the same as when I try to restore from within Windows.
Posts: 56
Threads: 7
Joined: Dec 2023
Reputation:
0
The better question is, why take up needless space. In fact you just said that HBS does not use c:\boot, but extracts a .win from a created .iso. That's a waste.
Posts: 56
Threads: 7
Joined: Dec 2023
Reputation:
0
That makes since. It's just that, of the dozen or so imaging apps I've used, I've never had one behave this way. The way it works now, you're asking users to use 1gb+ more space simply because there are essentially 2 PEs. Maybe, I'm the only one, but to me that's odd. Just have both functions use the same PE. The fact that you're asking the HBS to extract a wim from an iso every time you initiate a hot restore baffles me. What HBS user is not going to add the boot menu? My guess is maybe a single person, maybe.
Basically, store the iso used to extract the wim on hot restore to prevent recreating an emergency disk, so as to not use the bootloader wim (which is possible). To me that doesn't make sense.