WAPTEXIT

[cedar2]

Hello,

"WAPTexit.exe," which is supposed to launch when computers shut down to apply updates, isn't always working on my network.

I tested it on two Windows 7 machines that have pending updates.

WAPTexit is enabled in the local group policy for shutdown.

On the first 64-bit machine, it doesn't launch at all, while the other 32-bit machine works fine. Is there a connection? It seems to be random, depending on the computer. Is there something I need to enable on the machines for WAPTexit to launch?

Note that when launched manually, WAPTexit does offer to install the updates.

Any ideas?

[agauvrit]

Good morning,

• - Is this definitely Windows 7 Professional?
  - Is there an additional configuration manager that might be forcing GPOs (KoXo? IACA?)
  - What is the output of the command:

Code: Select all

wapt-get add-upgrade-shutdown

We should be updating our documentation very soon; the update includes a debug for the WAPTexit non-functioning.

Sincerely,

Alexander

[cedar2]

Hello,

"- Is this definitely Windows 7 Professional?"

--> Yes

"- Is there an additional configuration manager that might be forcing GPOs (KoXo? IACA?)"

--> No

"- What is the result of the command: wapt-get add-upgrade-shutdown?"

--> None

Thank you

[cedar2]

"- What is the result of the command: wapt-get add-upgrade-shutdown"


--> I specify that wapexit.exe was already present in the local shutdown policies.

[cedar2]

Surprisingly, when I delete wapt-exit.exe from the local policies and then manually add it back, it starts working.

Yet the original path is correct: "c:\wapt\waptexit.exe".

I can't do this on every computer in my network; it would take me weeks!

[sfonteneau]

Good morning

Attached you will find a portion of the upcoming documentation, which will be updated in a few days:

Could you please send us the compressed folder c:\\windows\\system32\\GroupPolicy\\ from a corrupted machine so we can understand the problem? To the address sfonteneau@tranquil.it

Code: Select all

WAPT Exit ne se lance pas
--------------------------

Malgré la présence du script dans les stratégie locales d'arrêt de la machine, WAPTexit.exe ne se lance pas à l'exinction du poste.


Résolution: Hybrid shutdown
+++++++++++++++++++++++++++

Il faut désactiver l'arrêt hybride de Windows 10, qui cause par ailleurs beaucoup d'autres comportements étranges, ce qui rétabli l'execution des scripts à l'extinction de la machine.

L'arrêt hybride peut être désactivé en précisant une valeur dans le fichier :file:`wapt-get.ini` de l'agent WAPT : :ref:`waptexit_ini`

Un paquet WAPT existe pour cela, `tis-disable-hybrid-shutdown <https://store.wapt.fr/wapt/tis-disable-hybrid-shutdown_1.0-2_all.wapt>`_.


Résolution: Windows Home édition
++++++++++++++++++++++++++++++++

Les GPO n'étant pas présentes sur un ordinateur home édition, il est normal qu'elles ne s'éxécutent pas.

La solution de contournement est d'utiliser une taches planifiée appelant :file:`C:\\wapt\\wapt-get.exe` et en paramètre :file:`upgrade`


Résolution: GPO locale corrompue
++++++++++++++++++++++++++++++++

Il peut arriver que les stratégies de groupes locales de la machine soient corrompues.

Une des solutions possible est de supprimer les stratégies locales actuelles pour résoudre le soucis:

Supprimer le fichier :file:`c:\\windows\\system32\\GroupPolicy\\gpt.ini`

Puis relancer l'installation de la tache d'extinction :

.. code-block:: bat

  wapt-get add-upgrade-shutdown

Si le problème se reproduit, cela signifie peut être qu'une autre application manipule également les GPO.

[cedar2]

Email sent.

Thanks for the documentation!

Performing this step manually on a corrupted machine works:


Delete the file: `c:\\windows\\system32\\GroupPolicy\\gpt.ini`
then
`wapt-get add-upgrade-shutdown`.


I'm now going to deploy a script to automate this and will keep you updated on the progress.

[Jimmy64]

Hello,

were you able to find the gpedit entry that modifies your local strategies for wapt in order to extract the registry base key?

[sfonteneau]

I was able to perform a diagnostic using the cedre2 file.

Therefore, the file C:\Windows\System32\GroupPolicy\gpt.ini appears to be corrupted.

Here is the content:

Code: Select all

gpcmachineextensionnames =[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{D02B1F72-3407-48AE-BA88-E8213C6761F1}][{A9B8D792-F454-11DE-BA92-FDCF56D89593}{0F6B957D-509E-11D1-A7CC-0000F87571E3}][{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}]

We can see that it's already quite abstract.

Okay, let's break it down:

Code: Select all

[{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}]   

This is the machine shutdown script

Code: Select all

[{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{D02B1F72-3407-48AE-BA88-E8213C6761F1}]

It's WSUS according to Google

And finally:

Code: Select all

[{A9B8D792-F454-11DE-BA92-FDCF56D89593}{0F6B957D-509E-11D1-A7CC-0000F87571E3}]

When you search on Google, not much comes up, unless you search for this:

Code: Select all

{A9B8D792-F454-11DE-BA92-FDCF56D89593}

We come across a wpkg script
https://github.com/cleitet/wpkg-gp/blob...ter.py#L27

I therefore assume that this machine had wpkg installed. It must have been uninstalled, but the key remained in the file.

When Microsoft parses the different keys in order, it gets stuck on the wpkg key and doesn't proceed any further, therefore not executing the one we're interested in. Too bad...

So all you need to do is delete the key in the file or switch the one from wapt beforehand and everything will be back to normal.

For the test, delete the key:

Code: Select all

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy

Then do a

Code: Select all

gpupdate /force

The registry key will be recreated correctly.


For Jimmy64

It's the group policy options (GPOs) that should modify the registry, not the other way around! Otherwise, you'll encounter problems, perhaps not immediately, but eventually.

[cedar2]

Thank you so much for all this information, I should be able to manage with that!