User Profile Service service failed weirdness

[FragglePete]

Just coming up to the last few machines left to deploy 1607 too - largely gone ok but a few little issues which we will just have to deal with as and when.

 

One that has me a little puzzled is when I sometimes go to log onto a random machine, I get the following error:

 

The User Profile Service service failed the sign-in.

The remote procedure call failed and did not execute.

 

See the picky:

 

I hit ok, and try logging in again and all seems well again.

 

Got me scratching my head a bit this has...... going to do a few checks on AD and DNS just to make sure everything is well, but most puzzling!

 

Any ideas?

 

Pete

[abaxter2]

Hi Pete,

 

Microsoft have just released KB3176934 ( https://support.microsoft.com/en-us/help/12387/windows-10-update-history ) and listed in the improvements is:

 

"Improved reliability of Network Controller, DNS server, gateways, Storage Spaces Direct, Group Managed Service Accounts, remote procedure calls (RPC), PowerShell, Internet Explorer 11, printer pairing and interoperability, the Windows kernel, Media Core, Windows Store, Connected Standby, Cluster Health service, the Hypervisor debugger and platform, and Active Directory."

 

Only problem tho is that it is not installing nicely via WSUS :-(

https://social.technet.microsoft.com/Forums/scriptcenter/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral

[FragglePete]

Thanks for that; much appreciated. If WSUS is being a bugger then it's the challenge of applying this .MSU file another way. Bit late to be added into MDT as we've rolled out 95% of the machines now.

 

Pete

[disk]

Are you running Visual Studio 2015 per chance? We experienced the same error (on Windows 8.1 and 10) after deploying VS2015 through SCCM along with Windows. It appears as though it enters some files into the Default User profile (appdata->roaming) because there hasn't been another user profile created and the way the installer works. We deleted the Microsoft folder found under appdata/roaming and it fixed the Default User profile which then allowed all other users to properly sign in. That was our experience any way.

 

*edit* The Microsoft folder that we removed to correct the sign on issue was in AppData/Local, not roaming.

Edited August 24, 2016 by disk

[mullet_man]

I've noticed this a lot too on my W10 devices ive deployed so far this summer. I've also noticed "bad stub" errors, been really flaky this release along with the WSUS issues ABaxter has mentioned it's been a bit of a pain.

 

ABaxter2 apparently adding the 2 latest KBs to MDT will get the WSUS step working again.

 

I was thinking of changing my WSUS GPO so my window 10 machines get their updates online, thus allowing said KBs to install which should then play nicely with WSUS.

 

Just a thought so far anyway, hopefully Microsoft will come up with a fix for the WSUS issue.

[angrycomputingteacher]

I get this on some of my PCs.

[ITGuyWestMidlands]

What type of profiles are you using? Local, roaming, mandatory?

[FragglePete]

I've noticed over the last couple days all sorts of weirdness - and from what is written here and elsewhere it would appear it's not me but this dodgy build! So, relieved in a way but now annoyed that some 550 devices deployed now have to be looked at again before the term starts.

 

I've been getting these 'User Profile Service' errors, bad stub errors when clicking on Start Menu items, Windows updates appearing to get stuck and on occasions stuck on 'preparing windows' on logon.

 

Grrrr.... so annoyed.

 

Still, .msu added to MDT for the handful of machines we have left. Using BCX Tools so can initiate a package task on the domain that installs this update (tested remotely and appears to work well) - just need to get everything fired up over the next few days and get the update installed. Hopefully this will settle things down abit.

 

Just to add; I'm using Redirected Folders - not using profiles.

 

Pete

[mullet_man]

Am using local profiles with redirected start menu.

 

Thanks FragglePete, like you say glad it's not just me with the same issues.

 

One of the new updates was a servicing update so hopefully that will fix the issue.

 

I haven't deployed it no where near as many devices but like you say it's a dodgy build indeed, at first I thought my reference image was messed up.

 

You need to make sure you add the two new KBs to MDT the cumulative update and the servicing update for the windows update step to work so am guessing the WSUS issue is fixed by one of those kbs.

[FragglePete]

Am using local profiles with redirected start menu.

 

Thanks FragglePete, like you say glad it's not just me with the same issues.

 

One of the new updates was a servicing update so hopefully that will fix the issue.

 

I haven't deployed it no where near as many devices but like you say it's a dodgy build indeed, at first I thought my reference image was messed up.

 

You need to make sure you add the two new KBs to MDT the cumulative update and the servicing update for the windows update step to work so am guessing the WSUS issue is fixed by one of those kbs.

 

Indeed - so from that I'm installing the following:

 

KB3176934

KB3176936

KB3176495

 

(I noticed another cropped up today also)

 

Pete

[FragglePete]

Just another update....

 

Just applied remotely to a machine at work and after the restart I noticed it started pulling in other updates from WSUS again. So, fingers crossed.

 

I'll test on a few more machines tomorrow before committing to the domain.

 

Pete

[mullet_man]

Thanks for the update Pete, I did some tweeting when the issue first happened and again yesterday and got this reply about which two KBs were needed for MDT to work.

 

 

As well as WSUS let's hope it fixes the issues we've both been having.

[abaxter2]

If you are still building machines then yes adding the updates as packages in MDT will mean that the build works well with no errors and for the machines that need these updates as I said at first they do not install well (lots of fails) but I am now finding that after a couple of reboots they are installing so fingers crossed they have fixed the issues as I really do not want to see these issue once the students are back - I am finding with the latest build things are looking better

[mullet_man]

I've deployed it to about 30 staff laptops, but haven't imaged my IT suites as yet due these issues. Going to image them next week with those KBs applied in MDT. Fingers crossed.

[abaxter2]

I think I have found why Windows updates are playing up! It looks like it is down to how Windows Update Delivery Optimization is delivering updates - I would only like my updates to come from my WSUS server and to do this you need to set the following:

 

Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization

 

Select "Download Mode" and select "Bypass"

 

After a gpupdate / force I then see under the client windows update setting > "Choose how updates are delivered" that it now states some settings are managed by your organization and that "Download windows updates and apps from other PC's" is turned off :-)

 

Now all my updates come from WSUS only and things are looking up!

 

More information here:

https://support.microsoft.com/en-gb/kb/3088114

https://blogs.technet.microsoft.com/mniehaus/2016/08/08/using-wsus-with-windows-10-1607/

https://blogs.technet.microsoft.com/mniehaus/2016/08/16/windows-10-delivery-optimization-and-wsus-take-2/

 

So hopefully this will help anyone who has already gone to build 1607 and trying to get the latest updates to install smoothly.

[mullet_man]

Thanks abaxter2, I'll have a look at that.

 

Are they updating from WSUS before the latest KBs have been applied?

[abaxter2]

Yes they have always checked into WSUS its just how the clients download the updates as without the setting i mentioned above they download from wsus and other clients on the network - I only want my clients to get their updates from my wsus server and since I have applied the above setting I mentioned my clients are downloading and installing updates much better and no fails yet. I am still to test if the issue with the MDT task of running windows update is fixed as my build images are updated when a new update is released / added as packages in MDT and are building fine it was just the clients that had already been built but with this GPO in place all is looking better. Edited August 27, 2016 by abaxter2

[mullet_man]

Yes me too so I'll make that change in my gpo too. Would leaving the setting on allow say staff laptops to download updates when at home? I haven't tested it myself but would be interested to know if that's how it works?

 

I've added both kbs to my MDT and deployed a test machine which has updated fine, when you click check for updates it takes a minute and reports back saying no updates are available so you can see it's working as it should now. Hopefully this is the last of this issue.

[abaxter2]

I was hopeful that this would be the end of the update issue but it seems its not as just found this:

 

"Hi everyone, and apologies for the frustration you're experiencing. This thread calls out several different symptoms, for each of which I'll provide guidance. Note that Configuration Manager will exhibit the same symptoms as each of the scenarios below.

 

1. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs

This is by design. WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. As folks have noted, these post-install steps [and the general way that this update was released] caused unnecessary pain and confusion. We'll choose a less disruptive strategy for future WSUS updates.

 

2. Clients have upgraded to 1706 using Anniversary Update, but cannot get Cumulative Updates

This is a bug in the Windows client that will be fixed in an upcoming cumulative update. In the meantime, clients may experience some delay in getting the monthly content, but they will eventually download it. The workaround here is to simply wait longer than usual, or to scan directly against Windows Update if you've waited several days and haven't seen any download success in that time.

 

3. WSUS can sync/distribute feature updates (such as 1511), but cannot deploy the 1607 feature update

This is a newly reported issue that we are currently investigating. Again, the workaround is to pull the 1607 feature update from Windows Update instead of WSUS. We understand why you might not want to pull such a large file from the Internet once for each of your clients, and are figuring this out as soon as we can. We'll share further updates on the investigation as they become available."

 

This was posted on the Friday the 27/08/2016

 

Full information here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/5521e7f1-fa2d-4867-a47c-b276c66e6a82/windows-10-anniversary-update-1607?forum=winserverwsus&tduid=(0f63bbc40e612779a916a85b535a6610)(256380)(2459594)(TnL5HPStwNw-X11ReOQTIgIvPEwgfvkr0Q)()

[mullet_man]

I've made adjustment to my GPO that changes the delivery optimisation setting to Bypass. So far I haven't found it any better, the updates are getting stuck at 0%, then download, then disappear, then re-download but don't seem to install. How long does it normally take?

 

Hopefully as per your post, the updates will eventually download.

 

I've been back in today, and have successfully imaged two IT rooms, both imaged fine and updates ran during the MDT TS. I then ran 3 more devices which needed imaging only to find they got stuck as per the original issue.

 

It's been one big massive cock, I waited a year to start my Windows 10 deployment in the hope all the issues would be ironed out by then but it's been a disaster. Am glad at the minute it's only going to be a phased rollout to our newer machines.

 

Thanks for keeping us updated, the big irony is the line about clients not being able to download cumulative updates will be fixed in a future cumulative update.

[FN-GM]

I am having this issue on odd machines, we use local profiles on LTSB 2015. Only fix I have found is deleting the profiles on the machine.

[FragglePete]

We're getting the odd machine that seems to get stuck pulling down the updates even after these latest KBs have been applied. Usually just leaving the thing alone and trying later seems to work.

 

Pete

[mullet_man]

We're getting the odd machine that seems to get stuck pulling down the updates even after these latest KBs have been applied. Usually just leaving the thing alone and trying later seems to work.

 

Pete

 

 

As a test am going to leave this laptop on and see if it updates, been on now for a good 10 mins.

 

How long does it taken normally?

[FragglePete]

[ATTACH=CONFIG]38498[/ATTACH]

 

As a test am going to leave this laptop on and see if it updates, been on now for a good 10 mins.

 

How long does it taken normally?

 

Some machines not very long, others it's taken over a day!!!!!

 

Pete

[ITGuyWestMidlands]

As a quick fix you could try adding your users to the donain guests group as these should get deleted off at log off.

 

I holding back on windows 10 for another 6 months at least, can be doing with out these headaches atm.

Edited August 31, 2016 by ITGuyWestMidlands