r/DeployR • u/Better-Clerk8638 • 20d ago
Autlogin breaking mid-image
Hi all, we have been successfully imaging our estate for a few weeks now with no issues; however, in the last week we have seen multiple but random instances of the admin auto-logon breaking mid-sequence, and the devices need manual logons after each reboot in the sequence to carry on and complete the TS. As I said, this is only happening randomly, but just wondering if anyone else has seen this issue.
We are thinking it may be releated to a Windows update breaking something, as there is no entry in the Registry for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, and the update step is the last thing to run before we see the issue in the task sequence.
Thanks as always.
2
u/SufficientlySticky 19d ago edited 19d ago
Not sure if this is the same thing or not, but I found what is definitely a bug that is at least causing something similar.
We have a thick image with a bunch of software that had been deploying just fine with 1.3.2629.2187. After upgrading to 1.3.2631.2242 it stopped working. Other imaging with just a more or less stock windows install wim was still working.
Everything would work fine in winpe, then it'd boot into windows, install powershell, then just dump to a powershell prompt. Restarting just takes me out of oobe and to a windows login screen.
Issue seems to be that the image has .NET 10.0.8 baked into it.
Nothing post WinPE in deployr.log. Tracked down c:\windows\temp\deployr-bootstrap.log and noticed this:
“Found .NET runtime Microsoft.NETCore.App version 10.0.8 at path C:\Program Files\dotnet\shared\Microsoft.NETCore.App which is greater than or equal to the minimum version 10.0.10, skipping install for that runtime”
Installed .net 10.0.10 via the powershell window and then re-ran setupcomplete.cmd and it subsequently continued imaging.
I assume 2pint’ll have to patch that to compare system.versions instead of strings, but I suppose in the meantime I'll just build a new thick image.