Thanks, Ben!

This is a bit outside of the scope of my normal job as I am an engineering PM and not responsible for this update, however, to anyone who is having this issue (per case #113101010852186) would you kindly let me know:

• of seats affected

• Your e-mail address (I will add it to the case)
• Is an active deployment halted?
• Any additional troubleshooting logs or data you can share.

You can e-mail me at benh (at) Microsoft.com and include links to any files that are too large to e-mail. I will file the escalation within 24 hours. EDIT: If you do this, please put "RE: 113101010852186" in the subject line so that I don't miss your e-mail.

That said, the issue is known and a fix is being worked on. If I do add you to the escalation ticket, you will at least be kept informed of the progress via e-mail.

Thanks,

Ben

For those with BSOD's

Can you email me at susan-at-msmvps.com? (change the -at- to @)

I need some log files from you. They can be large so I will set up a way to get them transfered to Microsoft.

a. Obtain a full dump from affected computers

b. %windir%\logs\cbs\cbs.log

c. %windir%\inf\setupapi.dev.log

d. Regkey PendingFileRenameOperations (HKLM\System\Controlset001\control\session manager)

e. Check if the machine has MSKB 2533552 installed.

f. Document the repro steps that lead to the blue screen

For those where it's stuck at 33ish%

Can you email me at susan-at-msmvps.com (change the -at- to @) and we'll make arrangments to get the following log files emailed to Microsoft

They need the following info:

· %windir%\inf\setupapi.dev.log

· %windir%\inf\setupapi.ev*

· %windir%\inf\setuppi.app.log

· %windir%\Logs\CBS\*.* (Share all files in this directory, even the cab files)

· %windir%\WindowsUpdate.log

· The output hotfix.txt from wmic qfe > hotfix.txt (type in at a command prompt wmic qfe >hotfix.txt )

· MSINFO32 output (see How to use System Information (MSINFO32) command-line tool switches )