HBS ED and KB5101650: Issues with keyboard driver and PE Network

[al3x]

On a side note: I also get this error popup the first time I start PC Network Manager.
But this is nothing new and happened in earlier versions as well. PE Network Manager still used to start fine.

Ok, found a fix for this error message:
"TCP/IP Registry Compatibility" service needs to be running before starting PE Network Manager.

That can be done by adding this line before AppLoader to Winpeshl.ini:
"%SYSTEMDRIVE%\Windows\System32\net.exe", start tcpipreg

Code:

[LaunchApps]
"%SYSTEMDRIVE%\Windows\System32\wpeinit.exe"
"%SYSTEMDRIVE%\Windows\System32\net.exe", start tcpipreg
"%SYSTEMDRIVE%\Program Files\Hasleo Backup Suite\bin\AppLoader.exe"

Still don't know why PENetwork.exe crashes, though.
I ran it with "/debug" and the debug log in %temp% just stops at:

Code:

IN: CreateMainGUI

That could be tricky to find...

[Bespoken]

Adding "start tcpipreg" did not prevent the error popup for me. It might have delayed it a bit. And yes, the error only happens the first time that Network Manager is started.

I have added this to my ED build notes, and it if proves to be the real fix then that should be part of an HBS release.

[al3x]

Adding "start tcpipreg" did not prevent the error popup for me. It might have delayed it a bit. And yes, the error only happens the first time that Network Manager is started.

I have added this to my ED build notes, and it if proves to be the real fix then that should be part of an HBS release.

The syntax and order of execution were slightly wrong, sorry for that, I didn't test this properly.
I've fixed the command in my post.

[Bespoken]

Changed the order, but still got the error pop-up.

Interestingly, there is no wpeinit.exe in %SYSTEMDRIVE%\Windows\System32\ on my PC.

[al3x]

Are you sure your line is correct? I had to change it slightly.
For me, the popup is now gone after rebuilding the ISO.

And wpeinit.exe is only packed with WinPE builds, that’s why 

[Bespoken]

I must moved the original with the parameters with the quotation mark. Change that and no more error pop-up.

What do you mean "only packed with WinPE builds"? The Create Emergency Disk builds the WinPE.iso, but I could not find wpeinit.exe in the .iso either.

[admin]

Thank you @Bespoken and @al3x for your continued testing and sharing. Recently, Windows updates always bring all sorts of issues. I think we might have to consider implementing our own PE Network tool. Since we have no relevant experience, this will require some technical exploration first.

Regarding wpeinit.exe, it is a WinPE‑specific executable that only exists within the WinPE environment.

[al3x]

Thank you @Bespoken and @al3x for your continued testing and sharing.

You're welcome!

I think we might have to consider implementing our own PE Network tool. Since we have no relevant experience, this will require some technical exploration first.

Btw, I contacted the author of PE Network Manager and he wants to replicate the issue. I gave him some details about HBS and how to replicate, maybe he can come up with a fixed version

[admin]

Thank you @Bespoken and @al3x for your continued testing and sharing.

You're welcome!

I think we might have to consider implementing our own PE Network tool. Since we have no relevant experience, this will require some technical exploration first.

Btw, I contacted the author of PE Network Manager and he wants to replicate the issue. I gave him some details about HBS and how to replicate, maybe he can come up with a fixed version 

This is good news. Can you ask the author if it's possible to release an ARM64 version? Thanks.

[al3x]

I don't think ARM64 will be possible tbh. PE Network Manager is based on AutoIt and it doesn't seem like AutoIt currently supports ARM64 unfortunately.