Tranquil IT Forum

Hello,

I'm following up on the use of wapt-exit.exe.
I've noticed a problem, but I haven't been able to find the cause.

The description is:

wapt-exit.exe doesn't run automatically when the PCs shut down.
wapt-exit.exe runs automatically when the PCs restart.

What I've checked:

Hyperboot is indeed disabled by changing the HyperbootEnabled value to 0 in the registry via a domain GPO.
wapt-exit.exe is present in the local GPO.
In wapt-get.ini:

max_gpo_script_wait=180
pre_shutdown_timeout=180
hiberboot_enabled=0
allow_cancel_upgrade=1

Do you have any suggestions?

Thank you

olaplanche wrote: ↑Apr 22, 2020 - 5:34 PM wapt-exit.exe does not run automatically when PCs are shut down.
wapt-exit.exe runs automatically when PCs are restarted.

I've never actually had that problem; for me, whether it's a restart or a shutdown, the shutdown scripts should work.

Have you tried putting something else in the GPO shutdown scripts?

Hello,

After various tests, my conclusion is as follows:

There are no issues with wapt-exit.exe; the problem occurs because the Group Policy client stops unexpectedly.
I won't bother you any longer with my problem.

Take care.

No worries, one last possibility: another GPO that might be crashing the entire GPO engine?

Unfortunately, we haven't found any other solution than a GPO to launch a program when the computer shuts down...

If anyone has any ideas

Actually, the Group Policy client service is configured by default to start automatically (trigger startup), which means the service can stop if it's not doing anything, and then a trigger can restart it at any time...

I still need to figure out why it doesn't restart automatically every time I shut down the PC!

Thanks

Hello,

I need some information:

At home, do you only use the `hiberboot_enabled=0` option in the `wapt-get.ini` file to disable Windows 10 Hyperboot? Nothing in a Group Policy Object (GPO)?

I realize that on my personal PC, where I use WaptStarter, I have the registry key `HKLM\CurrentControlSet\Control\Power\HilbernateEnabled=1` and the `hiberboot_enabled=0` option in the `wapt-get.ini` file, and it works perfectly! If I look in the GUI (Control Panel\All Control Panel Items\Power Options\System Settings), I can see that Fast Startup is disabled!

At work, I have the `HKLM\CurrentControlSet\Control\Power\HilbernateEnabled` registry key set to 0 by a GPO and the `hiberboot_enabled=0` option in the configuration file!

I'm starting to wonder if that's the problem! What exactly does the `hiberboot_enabled=0` option do in the config file? I have a feeling it's not the same thing as the registry key!

Thanks

You're not looking at the correct registry key:

https://github.com/tranquilit/WAPT/blob ... n.py#L3539
https://github.com/tranquilit/WAPT/blob ... ce.py#L221

or perhaps the key value needs to be changed?

Ah yes,
I got confused when manually checking the registry...
But I do have the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled key set to 0 by the GPO.
So the hiberboot_enabled=0 option in the config file does the same thing as the GPO...
So it all fits together, everything's fine on that end, darn...

Thanks!

When you say personal PC, do you mean a home Windows installation?

No, it's a Windows 10 Enterprise