Windows 2022 build failing "Restart Required" after second Windows Feature Install

[markatky46]

Any help greatly appreciated. Trying to do a Windows 2022 build. This is a brand new build for us. Setup all my packer.json the same as MS except a few amendments as we are publishing to a shared image gallery. Windows 2019 works fine with very similar code.

==> azure-arm: Provisioning with powershell script: /agent/_work/1/s/runner-images/images/win/scripts/Installers/Install-WindowsFeatures.ps1
azure-arm: Activating Windows Feature 'NET-Framework-Features'...
azure-arm: Windows Feature 'NET-Framework-Features' was activated successfully
azure-arm: Activating Windows Feature 'NET-Framework-45-Features'...
==> azure-arm: Install-WindowsFeature : The request to add or remove features on the specified server failed.
==> azure-arm: The operation cannot be completed, because the server that you specified requires a restart.
==> azure-arm: At C:\Windows\Temp\script-632d7198-156f-a353-2c7a-86227419bbc6.ps1:16 char:19
==> azure-arm: + $result = Install-WindowsFeature @arguments
==> azure-arm: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> azure-arm: + CategoryInfo : DeviceError: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exce
==> azure-arm: ption
==> azure-arm: + FullyQualifiedErrorId : DISMAPI_Error__Failed_Reboot_Required,Microsoft.Windows.ServerManager.Commands.AddWindow
==> azure-arm: sFeatureCommand
==> azure-arm: Failed to activate Windows Feature 'NET-Framework-45-Features'
==> azure-arm: At C:\Windows\Temp\script-632d7198-156f-a353-2c7a-86227419bbc6.ps1:24 char:9
==> azure-arm: + throw "Failed to activate Windows Feature '$($feature.name)'"
==> azure-arm: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> azure-arm: + CategoryInfo : OperationStopped: (Failed to activ...rk-45-Features':String) [], RuntimeException
==> azure-arm: + FullyQualifiedErrorId : Failed to activate Windows Feature 'NET-Framework-45-Features'
==> azure-arm:

I have seen in the Install-WindowsFeatures.ps1 that it explicitly states no restart. This is not happening on my Windows 2019 build.

[markatky46]

Turns out this was my error. I had used my Windows 2019 scripts as a base and failed to change the toolset to 2022 from 2019