Tranquil IT Forum

I installed a test machine with Windows 10 version 1903. The console correctly displays the machine, and I launch my pending packages. When I run a check, the console correctly displays all my packages that are waiting to be downloaded.

However, when I shut down or reboot, WAPTEXIT does not launch. I tried rebooting several times, but without success.

I performed a test by running waptexit.exe, and the installations then launched correctly.

Does waptexit appear correctly in the shutdown scripts in the local GPO? (gpedit.msc)

Yes, it does appear in the local GPO

And also in gpresult /h wapt.html?

I don't have WAPT in the gpresult

and a gpupdate /force command?

You should have this:

I tried it, and it tells me there's an application waiting, but it's a different application that isn't working. It appears in the event logs, but not Wapt; it's as if Wapt hasn't registered itself in the tasks

With Windows 10, I already encountered a case last week where a local GPO wouldn't apply because a domain GPO wasn't working...

I corrected the GPOs that were in error (damn SMB1 not enabled on W10) following that and the forced installation of the wapt-conf-policy
waptupgrade package to recreate the WAPTEXIT task launches with the display bug

Glad it's working again.

Mathieu wrote: ↑Oct 1, 2019 - 2:19 PM Damn SMB1

Joking aside, I'm very curious to know why you need to enable SMB1 on your Windows 10