Client 0.11.12, Windows 10 1709 - Reboot fails

[TrialAndError]

FogClient 0.11.12, Windows 10 1709 - Reboot fails after joining domain

Regulary the reboot fails after joining domain.
Sometimes the service fails to start (even after reboot) until it is started manually.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 16.01.2018 03:41 Client-Info Client Version: 0.11.12
 16.01.2018 03:41 Client-Info Client OS:      Windows
 16.01.2018 03:41 Client-Info Server Version: 1.4.4
 16.01.2018 03:41 Middleware::Response Success
 16.01.2018 03:41 HostnameChanger Checking Hostname
 16.01.2018 03:41 HostnameChanger Hostname is correct
 16.01.2018 03:41 HostnameChanger Attempting to join domain
 16.01.2018 03:41 HostnameChanger Success, code =  0
 16.01.2018 03:41 Power Creating shutdown request
 16.01.2018 03:41 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 16.01.2018 03:41 Bus Emmiting message on channel: Power
 16.01.2018 03:41 Power Attempt 1/6 to shutdown computer
 16.01.2018 03:41 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:46 Power Attempt 2/6 to shutdown computer
 16.01.2018 03:46 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:51 Power Attempt 3/6 to shutdown computer
 16.01.2018 03:51 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 03:56 Power Attempt 4/6 to shutdown computer
 16.01.2018 03:56 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:01 Power Attempt 5/6 to shutdown computer
 16.01.2018 04:01 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:06 Power Attempt 6/6 to shutdown computer
 16.01.2018 04:06 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:11 Power Gracefull shutdown requests failed, attempting to force shutdown
 16.01.2018 04:11 Power Attempt 1/3 to shutdown computer
 16.01.2018 04:11 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:16 Power Attempt 2/3 to shutdown computer
 16.01.2018 04:16 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:21 Power Attempt 3/3 to shutdown computer
 16.01.2018 04:21 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:26 Power Force shutdown requests failed, bypassing any shutdown blocks
 16.01.2018 04:26 Power Attempt 1/3 to shutdown computer
 16.01.2018 04:26 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:31 Power Attempt 2/3 to shutdown computer
 16.01.2018 04:31 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:36 Power Attempt 3/3 to shutdown computer
 16.01.2018 04:36 Power --> API call returned 1, will re-attempt in 5 minutes
 16.01.2018 04:41 Power ERROR: Failed to bypass shutdown blocks, entering saftey net to ensure a shutdown
 16.01.2018 04:41 Power Issued shutdown request, will re-issue in 5 minutes
 16.01.2018 04:46 Power Issued shutdown request, will re-issue in 5 minutes```

[Joe Schmitt]

@TrialAndError @UWPVIOLATOR v0.11.13 of the client (in the newest RC) patches the win1709 issues, thank you for your help debugging this!

[Joe Schmitt]

@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.

[TrialAndError]

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?

[Joe Schmitt]

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.

[kwisher]

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.

[Sebastian Roth]

@kwisher Do you actually see the same messages in the fog-client log? Please post your logs here as well.

[UWPVIOLATOR]

I am having the a similar issue. Windows 10 EDU 1709. FOG 1.4.4

[Joe Schmitt]

@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!

[UWPVIOLATOR]

@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]

@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.

[x23piracy]

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

[UWPVIOLATOR]

@Joe-Schmitt Another thing I am seeing is on 2 different models. HP Elitebook 840 G1 and a HP Elitedesk 8300. The 840 will start the fog service, name and join domain but not do the final reboot. The 8300 doesn’t start FOG. Setupcomplete.cmd worked as the FOG service is set to Automatic but again its a reboot to start up.

[Joe Schmitt]

@UWPVIOLATOR @x23piracy can you try the following stops on a problematic machine?

• In an administrative CMD, stop the fogservice if it is still running: net stop fogservice
• Download and extract this file anywhere on the machine: PowerDebugger.zip
• Run the Debugger.exe contained in the extracted folder as Administrator
• Type the following commands into the debugger’s prompt (one at a time, and pressing enter after each line)

bus mode server
power restart

The debugger will then schedule the client’s restart process in 60 seconds. Can you let me know if it successfully restarts the machine? If not I’ll need the full output of the Debugger window.

[Joe Schmitt]

@UWPVIOLATOR @x23piracy after running the debugger in the prior post, can you also try installing this build of the client on a few machines: https://build.jbob.io/Client/nightly/01-32-2018-win-dependencies-01/SmartInstaller.exe ?

It likely wont fix the shutdown issue, but it should allow the client to consistently start up with Windows.

[TrialAndError]

@joe-schmitt

“power restart” did restart my machine. Success!

[Joe Schmitt]

@TrialAndError @UWPVIOLATOR @x23piracy @dclark I believe I have isolated the issues with Windows 1709 and patched them. Could you try installing this build of the client on a few machines to test? (You may need to hit Reset Encryption Data for the hosts if you are uninstalling an existing FOG Client and installing this build). With any luck it will fix all issues with the service failing to start, and not shutting down the computer correctly.

https://build.jbob.io/Client/nightly/02-01-2018-win1709-04/SmartInstaller.exe

NOTE: This is a nightly build and is not production compatible! Imaging it may produce security warnings from Windows or your anti virus software.

[TrialAndError]

@joe-schmitt

Sorry,

my machine still does not reboot. The desktop client shows up and vanishes but no power event is executed.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 02.02.2018 09:07 Client-Info Client Version: 0.11.12
 02.02.2018 09:07 Client-Info Client OS:      Windows
 02.02.2018 09:07 Client-Info Server Version: 1.4.4
 02.02.2018 09:07 Middleware::Response Success
------------------------------------------------------------------------------

 02.02.2018 09:07 Service Sleeping for 132 seconds
 02.02.2018 09:08 Power Creating shutdown request
 02.02.2018 09:08 Power Parameters: /r /c "FOG PowerManagement" /t 0
 02.02.2018 09:08 Bus Emmiting message on channel: Power
 02.02.2018 09:08 Power Attempt 1/6 to shutdown computer
 02.02.2018 09:08 Power --> API call returned 0, will re-attempt in 5 minutes
 02.02.2018 09:09 Power ERROR: Could not create shutdown command from request
 02.02.2018 09:09 Power ERROR: Die Laufzeitbindung kann für einen NULL-Verweis nicht ausgeführt werden.

[Joe Schmitt]

@TrialAndError if you set the service to delayed start, or manually stop and start up the client after boot, then does it work?

[TrialAndError]

@joe-schmitt
I manually stopped/started FOGService but no effect.

[UWPVIOLATOR]

@joe-schmitt I installed your nightly client build. It does not work and I can not even start the service. Gives me this error.