Not sure if list of 20+ updates included any for TMG 2010 or not, so I'm listing in both forums.
Windows reboots (no blue screen) shortly after classpnp.sys is loaded, as seen during Safe Mode boot. When choosing Enable Boot Logging option at F8 startup, [e:\windows\Ntbtlog.txt] doesn't appear to be created (e: is the letter assigned to the existing system partition when in Recovery Console). As suggested by http://support.microsoft.com/kb/275735: "If the computer stops responding (hangs) before Session Manager (Smss.exe) is initialized, the log file [%windows%\Ntbtlog.txt] is not created because data cannot be committed from the registry to the file."
1) I located the registry files of the failed system - can this pre-file format of the boot logging be retrieved from the registry?
As suggested by http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-repair-steps-for-no-boot-issues.aspx, booting from the Server 2008 R2 DVD and choosing "Command prompt" and running X:\sources\recovery\startrep.exe results in no %WINDIR%\System32\LogFiles\Srt folder, much less the anticipated SrtTrail.txt log file in it. But the GUI reports:
Problem Signature 01:6.1.7600.16385
Problem Signature 02:6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: -1
Problem Signature 05: ExternalMedia
Problem Signature 06: 1
Problem Signature 07: NoOsInstalled
OS Version: >6.1.7600.2.0.0.2561
Locale ID:1033
2) Is this the same information expected to be logged to SrtTrail.txt?
3) If not, why might this file not be created?
4) Either way, does the info above suggest what is wrong? "NoOsInstalled" doesn't sound very accurate.
5) Is there a way to uninstall or roll back the most recent round of updates?
As suggested by http://support.microsoft.com/default.aspx?scid=kb;EN-US;975484, the .vbs script resulted in removal of 2 POQ nodes, but now seems to reboot even faster than before, still upon appearance of classpnp.sys in Safe Mode.
Running sfc resulted in "there is a system repair pending which requires a boot to complete...", renaming e:\Windows\WinSxS\pending.xml allowed sfc to run successfully, with no problems detected.
6) The prescribed methods for running DISM haven't made any sense to me... where does C:\test\offline come from? It's not on my system. Even if it was, how would I specify which "packages" (I prefer to call them "updates") to remove?