Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, May 18, 2016 7:53 PM
Using a fresh Windows 10 Enterprise image with UWF enabled, after using the 'uwfmgr servicing enable' command and restarting, the system reaches the log in screen, shows "UWF-Servicing" as the account to log into with a password field, but does not log in as it is supposed to. Microsoft documentation states that this is supposed to happen automatically. But it doesn't. Is there a way to fix this?
All replies (7)
Thursday, May 19, 2016 2:40 AM
Please check Microsoft documentation and follow its guide to operate.
https://msdn.microsoft.com/en-us/library/windows/hardware/mt571993(v=vs.85).aspx
Firstly, enable antimalware support on Filter-enabled Windows 10 Enterprise device.
Secondly, Apply OEM updates to UWF-protected devices.
Thirdly, Apply Windows updates to UWF-protected devices.
In the third step, please notice this point: The default servicing account that is automatically created and used for servicing is named UWF-Servicing. It is important that you do not have a user account that has that same name on a device before starting UWF servicing.
I and my colleagues follow the guide and make it, smart as you, can also achieve it smoothly.
Regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Thursday, May 19, 2016 12:59 PM
Teemo,
Thanks for the reply.
I have read the documentation thoroughly, updates have been applied and regardless, UWF still fails to act correctly. We've tested this on multiple machines, and get the same result every time. My hope is someone has encountered this before and has a fix for it.
Friday, May 20, 2016 5:39 PM
I was able to get it to work once, and only once. I had configured UWF, enabled the Windows Feature Embedded Logon, let it install its updates, then went into servicing mode, where it logged in, showed the screen saver, executed the master servicing script, and restarted. Now we can't get it to recreate that same scenario.
We've tried it on multiple machines, with different combinations of the embedded features activated, but no joy. We've even tried it on the preview for the anniversary release, but UWF is more broken on that build, causing blue screens on reboot after servicing mode is enabled.
Friday, March 3, 2017 10:35 PM
Did you ever figure this out? I am having a heck of a time with this on some new thin clients we ordered.
Friday, May 19, 2017 11:05 AM
Do you have auto logon enabled? Try turning it off. Worked for me!
Thursday, June 8, 2017 8:56 PM | 1 vote
I did a recent test with two Windows operating systems.
Windows Embedded 8.1 Industry - UWF service enable - When I rebooted the system, the screen saver popped up indicating that system update was running. After a while it rebooted, and came up to a lock screen. Behind the lock screen it showed the UWF-Service account was logged, but it never came back to the screensaver - the screen went black after a while. Eventually, the system rebooted back to the main account and I could see that Windows updates were installed and UWF was enabled.
Windows 10 IoT Enterprise (aka Windows 10 Enterprise LTSB 2016) - The system never logs and never shows the screensaver. it shows the lock screen and behind the lock screen the UWF-service account - no indication that it is logged in. The screen goes black after awhile. Eventually, the system rebooted back to the main account and I could see that Windows updates were installed and UWF was enabled.
UWF Servicing feature works, but there is really no indication that the update is really running or not. Since it can take some time to run, it may appear dead to the common user.
Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com
Wednesday, November 15, 2017 7:36 PM
Did you ever get this working? I tried Windows 10 Education v1703 and v1709 (clean installs and on different machines) and have the same issue, I get stuck on the UWF-Servicing account on the lock screen and it never does anything.