Mark Russinovich’s technical blog covering topics such as Windows troubleshooting, technologies and security.
Microsoft Customer Support Services (CSS) is one of the biggest customers of the Sysinternals tools and they often send me interesting cases they’ve solved with them. This particular case is especially interesting because it affected a large number of users and the troubleshooting process made use of one of Process Monitor’s lesser-known features. The case opened when a customer contacted Microsoft support reporting that several of their users would occasionally get this error message when loggging on to their systems:
This caused Windows to create a temporary profile for the user’s logon session. A user profile consists of a directory, %UserProfile%, into which applications save user-specific configuration and data files, as well as a registry hive file stored in that directory, %UserProfile%\Ntuser.dat, that the Winlogon process loads when the user logs in. Applications store user settings in the registry hive by calling registry functions that refer to the HKEY_CURRENT_USER (HKCU) root key. The user’s loss of access to their profile made the problem critical, because whenever that happened, the user would apparently lose all their settings and access to files stored in their profile directory. In most cases, users contacted the company’s support desk, which would ask the user to try rebooting and logging in until the problem resolved itself.
As with all cases, Microsoft support began by asking about the system configuration, inventory of installed software, and about any recent changes the company had made to their systems. In this case, the fact that stood out was that all the systems on which the problem had occurred had recently been upgraded to a new version of Citrix Corporation's ICA client, a remote desktop application. Microsoft contacted Citrix support to see if they knew of any issues with the new client. They didn’t, but said they would investigate.
Unsure whether the ICA client upgrade was responsible for the profile problem, Microsoft support instructed the customer to enable profile logging, which you can do by configuring a registry key as per this Knowledge Base article: How to enable user environment debug logging in retail builds of Windows. The customer pushed a script out to their systems to make the required registry changes and shortly after got another call from a user with the profile problem. They grabbed a copy of the profile log off the system from %SystemRoot%\Debug\UserMode\Userenv.log and sent it into Microsoft. The log was inconclusive, but did provide an important clue: it indicated that the user’s profile had failed to load because of error 32, which is ERROR_SHARING_VIOLATION:
When a process opens a file, it specifies what kinds of sharing it allows for the file. If it is writing to the file it may allow other processes to read from the file, for example, but not to also write to the file. The sharing violation in the log file meant that another process had opened the user’s registry hive in a way that was incompatible with the way that the logon process wanted to open the file.
In the meantime, more customers around the world began contacting Microsoft and Citrix with the same issue, all had also deployed the new ICA client. Citrix support then reported that they suspected that the sharing violation might be caused by one of the ICA client’s processes, Ssonvr.exe. During installation, the ICA client registers a Network Provider DLL (Pnsson.dll) that the Windows Multiple Provider Notification Application (%SystemRoot%\System32\Mpnotify.exe) calls when the system boots. Mpnotify.exe is itself launched at logon by the Winlogon process.The Citrix notification DLL launches the Ssonvr.exe process asynchronous to the user’s logon:
The only problem with the theory was that Citrix developers insisted that the process did not attempt to load any user registry profile or even read any keys or values from one. Both Microsoft and Citrix were stumped.
Microsoft created a version of Winlogon and the kernel with additional diagnostic information and tried to reproduce the problem on lab systems configured identically to the client’s, but without success. The customer couldn’t even reproduce the problem with the modified Windows images, presumably because the images changed the timing of the system enough to avoid the problem. At this point a Microsoft support engineer suggested that the customer capture a trace of logon activity with Process Monitor.
There are a couple of ways to configure Process Monitor to record logon operations: one is to use Sysinternals PsExec to launch it in the session 0 so that it survives the logoff and subsequent logon and another is to use the boot logging feature to capture activity from early in the boot, including the logon. The engineer chose the latter, so he told the customer to run Process Monitor on one of the system’s that persistently exhibited the problem, select Enable Boot Logging from the Process Monitor Options menu, and reboot, repeating the steps until the problem reproduced. This procedure configures the Process Monitor driver to load early in the boot process and log activity to %SystemRoot%\Procmon.pmb. Once the user logged encountered the issue, they were to run Process Monitor again, at which point the driver would stop logging and Process Monitor would offer to convert the boot log into a standard Process Monitor log file.
After a couple of attempts the user captured a boot log file that they submitted to Microsoft. Microsoft support engineers scanned through the log and came across the sharing violation error when Winlogon tried to load the user’s registry hive:
It was obvious from operations immediately preceding the error that Ssonsvr.exe was the process that had the hive opened. The question was, why was Ssonsvr.exe opening the registry hive? To answer that question the engineers turned to Process Monitor’s stack trace functionality. Process Monitor captures a call stack for every operation, which represents the function call nesting responsible for the operation. By looking at a call stack you can often determine an operation’s root cause when it might not be obvious just from the process that executed it. For example, the stack shows you if a DLL loaded into the process executed the operation and, if you have symbols configured and the call originates in a Windows image or other image for which you have symbols, it will even show you the names of the responsible functions.
The stack for Ssonsvr.exe’s open of the Ntuser.dat file showed that Ssonsvr.exe wasn’t actually responsible for the operation, the Windows Logical Prefetcher was:
Introduced in Windows XP, the Logical Prefetcher is a kernel component that monitors the first ten seconds of a process launch, recording the directories and portions of files accessed by the process during that time to a file it stores in %SystemRoot%\Prefetch. So that multiple executables with the same name but in different directories get their own prefetch file, the Logical Prefetcher gives the file a name that’s a concatenation of the executable image name and the hash of the path in which the image is stored e.g. NOTEPAD.EXE-D8414F97.pf. You can actually see the files and directories the Logical Prefetcher saw an application reference the last time it launched by using the Sysinternals Strings utility to scan a prefetch file like this:
strings <prefetch file>
The next time the application launches, the Logical Prefetcher, executing in the context of the process’s first thread, looks for a prefetch file. If one exists, it opens each directory it lists to bring the directory’s metadata into memory if not already present. The Logical Prefetcher then maps each file listed in the prefetch file and references the portions accessed the last time the application ran so that they also get brought into memory. The Logical Prefetcher can speed up an application launch because it generates large, sequential I/Os instead of issuing small random accesses to file data as the application would typically do during startup.
The implication of the Logical Prefetcher in the profile problem only raised more questions, however. Why was it prefetching the user’s hive file in the context of Ssonsvr.exe when Ssonsvr.exe itself never accesses registry profiles? Microsoft support contacted the Logical Prefetcher’s development team for the answer. The developers first noted that the registry on Windows XP is read into memory using cached file I/O operations, which means that the Cache Manager’s read-ahead thread will proactively read portions of the hive. Since the read-ahead thread executes in the System process, and the Logical Prefetcher associates System process activity with the currently launching process, that a specific timing sequence of process launches and activity during the boot and log on could cause hive accesses to be seen by the Logical Prefetcher as being part of the Ssonsvr.exe launch. If the order was slightly different the next boot and log on, Winlogon might collide with the Logical Prefetcher, as seen in the captured boot log.
The Logical Prefetcher is supposed to execute transparently to other activity on a system, but its file references can lead to sharing violations like this on Windows XP systems (on server systems the Logical Prefetcher only prefetches boot activity, and it does so synchronously before the boot process proceeds). For that reason, on Windows Vista and Windows 7 systems, the Logical Prefetcher makes use of a file system minifilter driver, Fileinfo (%SystemRoot%\System32\Drivers\Fileinfo.sys), to watch for potential sharing violation collisions and prevent them by stalling a second open operation on a file being accessed by the Logical Prefetcher until the Logical Prefetcher closes the file.
Now that the problem was understood, Microsoft and Citrix brainstormed on workarounds customers could apply while Citrix worked on an update to the ICA Client that would prevent the sharing violation. One workaround was to disable application prefetching and another was to write a logoff script that deletes the Ssonsvr.exe prefetch files. Citrix published the workarounds in this Citrix Knowledge Base article and Microsoft in this Microsoft Knowledge Base article. The update to the ICA Client, which was made available a few days later, changed the network provider DLL to 10 seconds after Ssonsvr.exe launches before returning control to Mpnotify.exe. Because Winlogon waits for Mpnotify to exit before logging on a user, the Logical Prefetcher won’t associate Winlogon’s accesses of the user’s hive with Ssonsvr.exe’s startup.
As I said in the introduction, I find this case particularly interesting because it demonstrates a little known Process Monitor feature, boot logging, and the power of stack traces for root cause analysis, two key tools for everyone’s troubleshooting arsenal. It also shows how successful troubleshooting sometimes means coming up with a workaround when there’s no fix or you must wait until a vendor provides one. Another case successfully closed with Process Monitor! Please keep sending me screen shots and log files of the cases you solve.
I have this problem too at my computer at home. If my wife has been logged on to her account and I log on to mine this happens ~50% of the time.
ASFAIK we don't have any Citrix stuff installed so there's no fix for us. It's a bit weak by MS to not solve it properly themselves, since it's obviously a bug in how the cache manager interacts with the rest of the system at logon.
At least now I know how to find out what application the prefetcher will think was associated with the registry read so I could write a script tot delete those pf-files at logoff.
Several comments suggested a flaw in the file system regarding access sharing and file locks and targeted the Logical Prefetcher (LP) as the problem. However, these seem to miss the point, as the LP already utilizes read-only access and specifies full sharing. The problem in this case really lies with Winlogon because it requires exclusive access.
The article does identify a weakness of the LP in that 1) it cannot distinguish between simultaneous System processes that are non-related (such as the cached IO file operations) from those initiated by the launching process and 2) future LP activity can initiate unnecessary reads, specifically those from the previous unrelated System processes, which could cause collisions with Winlogon. The LP has been modified in Vista and Windows 7 to work around this issue as it pertains to the LP.
I wonder if the LP can be reengineered to only associate the simultaneous System processes that are actually initiated or indeed related to a launching process and also if Winlogon should be modified in a way to play more nicely? In the meantime, using the tools and debugging techniques outlined can help identify troublesome startup processes and a log-off script deleting the offending prefetch files can create a work around.
This is a very interesting and informative article, none the less.
We encounterd a similiar problem with our Antivirus. The Realtime Scanner accesses all ntuser.dat when the computer starts. When the user logs on quickly, nothing is reported. When the user logs on after some time, there is a sharing violation from Rtvscan.exe on the users ntuser.dat.
When the user logs on exactly when Rtvscan access his ntuser.dat, the Temporary Registry Profile problem occurs.
I sent procmon.log to the MS Engineers, but in my opinion they where not able to interpret the log file...they should be more engineers like Mark understanding the Windows logon process...
Yes, yes. The google Updater is the cause. I have this problem with Windows 7. when uninstalling Google updater I could go to a "termporary profile" normally in real time.
I can't believe no one has mentioned this yet... Was the official solution (or workaround) to this problem in the new client really to just sit there delaying the user's boot for 10 seconds while nothing happens? As someone who was forced for several years to use a networked Windows system that had hideously slow logins (we're talking several minutes minimum and up to 10-15 minutes and sometimes more during peak times), I shudder to think that software may be deliberately delaying this to an even further extent.
Or did I read it wrong and it's the program in the new thread which waits 10 seconds? Still seems a bit of a kludge because on systems where the login has different timing, this could cause services provided by the app to be unavailable for a few seconds after login apears to have finished. Fine for a human who can't react that fast, but I wonder how long it'll take for a company to file a bug along the lines of "Our script which does X and Y after [or during] boot using operations enabled by your software no longer works on 30% of our computers."
OK, just captured a similar race between spoolsv and winlogon on XP embedded.
This has been giving us major headaches alreay so I am glad I came over this thread to find the root cause. On our systems about 1 of 20 boots are failing because of this.
This was written to provide a means of reassociating profiles which have become detached from their accounts:
I'll admit that at this early stage of development there are still one or two scenarios which it can't handle. That said it does work well enough to get most users out of dissociated-profile trouble.
Sounds like you need to clean out your printer drivers and start reinstalling them until you find out which one is breaking logon.
The vast majority of these problems are caused by third parties hooking the logon in various ways. Microsoft can only be faulted for giving them the ability to shoot themselves in the foot, but they're still to blame for actually wrecking your user experience; blaming Microsoft for lack of foresight on the first implementation of a feature is pointless. XP & 2003 are long since out of mainstream support. The point of this blog is to show how you would determine which third-party component is doing it, so you can either disable it or make an informed bug report the developer.
Interesting artical and thanks for sharing!