Deployment of IEAK packaged build, via LocalSystem context causes Windows User Profile Service to crash

Won’t fix Issue #212439

Details

Created
May 14, 2014
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

deploy the IEAK built package, via LocalSystem context (e.g. ConfigMgr)
restart the PC
logon to the PC with a user account which has never logged onto that PC previously.
UPS crash occurs, the user cannot logon to the PC.

refer: http://social.technet.microsoft.com/Forums/en-US/43cb5946-9d82-4973-b8a1-4053aa688ba8/user-profile-service-failed-the-signin-user-profile-cannot-be-loaded-for-any-new-accounts?forum=w8itprogeneral

also: http://blogs.msdn.com/b/asiatech/archive/2014/01/30/new-user-gets-event-1509-after-deploying-ie9-10-11-packaged-by-ieak.aspx

I raised a Premier case for the IEAK-introduced issue. I suspect it is a defect in the CEIP/SQM client-side dll, in that the SQM blob is created in the default user profile, and when the transmission of the blob fails (or is denied due to an authenticating proxy or whatever), the file blob is abandoned, with the ACE/ACL inheritance broken, which leads to the UPS crash. As per my own testing, disabling CEIP in Windows, then performing the IE install (which honors the no-CEIP setting), then reverting the no-CEIP setting, is a barely-acceptable workaround. I’d prefer to see the “defective” SQM/CEIP code fixed thanks.

Expected Results:

UPS should not crash when a “new” user account logs on to the PC

Actual Results:

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Dave B.”

      Changed Assigned To from “Dave B.” to “Bob S.”

      Changed Assigned To from “Bob S.” to “IE F.”

      Changed Status to “Won’t fix”

    You need to sign in to your Microsoft account to add a comment.

    Sign in