Happening across multiple Windows OS versions, e.g.:

• https://community-tc.services.mozilla.com/worker-manager/proj-taskcluster%2Fgw-windows-2022-gui/errors
• https://community-tc.services.mozilla.com/worker-manager/proj-taskcluster%2Fgw-windows-11-24h2-staging/errors

May be related to moving the image building to packer, since time-wise this seems to be new since moving.

Typical error looks like:

LoadUserProfile('̈', &{Size:56 Flags:1 Username:0xc000433050 ProfilePath:<nil> DefaultPath:<nil> ServerName:<nil> PolicyPath:<nil> Profile:0}): LoadUserProfile: The device is not ready.

Originates from

Initial thoughts: maybe packer creates an image which does something special on first bootup?

Since headlessTasks is false at least in proj-taskcluster/gw-windows-2022-gui this failure is probably happening when Generic Worker tries to remap the AppData folder for the new task user it has created for the subsequent task run (after the reboot), i.e. not for the currently logged in task user, since LoadUserProfile is called to get an auth token in the case there is not an interactive desktop session for the user.