2 user registry handles leaked from registry user windows 2008

The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required. Attachments: Up to 10 attachments including images can be used with a maximum of 3. Something here might help. I'd start with the process IDs. Also try from a clean boot. This forum focuses on the operating system itself.

Yes, I'm aware. Applies to: Windows 8. The Windows operating system detected that your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. Included in the following details are four examples of the type of information that can appear in this event message:.

This event can be caused by apps that do not release their Registry keys before shutting down. This most often occurs when an app runs in the background and does not release its Registry keys when a user signs off, in which case Windows forces the Registry to unload. Active 7 years, 10 months ago.

Viewed 4k times. When the machine starts, I can see that it starts executing the Python script, and then I start seeing messages like the following in the event log: Windows detected your registry file is still in use by other applications or services.

The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. Improve this question. It looks as though you're running the Python scripts in the context of a user account that is being logged out before they are complete. That's expected on Server if the parent process exits, but shouldn't happen on according to the documentation.

How are the scripts being launched? I looked up the SID S These scripts are being launched by a scheduled task which runs after the system starts, and is supposed to be launched regardless of if my user account is logged in or not. I also gave my account the "log on as a batch job" user right.

Add a comment. Active Oldest Votes. Improve this answer. Harry Johnston Harry Johnston It may be that some your files are corrupted. Select Command Prompt Admin. Now Click Troubleshoot. Now click Advanced options and select Command prompt. Type Advanced Startup options, hit enter. Then click Advanced options and then Automatic Repair.

Hope it helps.