Client 0.11.12, Windows 10 1709 - Reboot fails
-
Hi,
not sure but i think i have the same issue with a 1709 image, it’s from the early 1709 days and i am sure that the spectre meltdown fixes are not involved here.
When i have a deployment next days i will try to deploy that image again and will report if i have the same there.
Regards X23
-
@Joe-Schmitt Same power error. It looks like it named and joined the domain but it did not reboot that final time. The registry settings are still there so that should of worked.
-
@joe-schmitt So I tired to run the KB and it doesn’t really run or show it ran but no error. I did do the registry edit and am testing now. But we are not using copyprofile because of the other issues, so hopefully the settings stick.
-
@UWPVIOLATOR @kwisher @TrialAndError so far it seems to be caused by a faulty Windows Spectre patch. See this thread for what hopefully is the solution: https://forums.fogproject.org/topic/11342/windows-10-fog-client-failing-to-restart/7
Please report back if applying the fix actually resolved the client issue!
-
I am having the a similar issue. Windows 10 EDU 1709. FOG 1.4.4
-
@kwisher Do you actually see the same messages in the fog-client log? Please post your logs here as well.
-
I’m seeing the same thing here with Win10-Pro 1709, educational volume license program. Imaging was working fine before this update. Hostname changer sems to run but the AD join does not. Hit and miss that AD join kicks off after manually rebooting.
-
Linking with https://forums.fogproject.org/topic/11342/windows-10-fog-client-failing-to-restart as @dclark has the same issue. It seems to be specific to 1709.
-
Just clean Windows 10 Education, no policies, default anti virus, no “tuning” at all.
The Client is part of the image, no sysprep.
What can I look for in the error log?
-
@TrialAndError we need a lot more information. For example what anti virus are you using? Do you have any restrictive policies on these computers? Any custom software that blocks shutdowns, or isn’t programmed correctly to handle them?
The error log indicates that the win32 api for shutdowns is being blocked. You should check the windows error log for potential messages. We also need to know how you got the client onto this computer. Did you image with it installed? If so did you use sysprep?
If I had to guess without any of that info, I would say it’s likely an antivirus program ignoring the clients valid binary signatures. But I would need more info to help beyond that.
