site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Posting?
Post a:
Post a:
Links: ·MS Apps FAQ ·Windows XP FAQ ·Windows 7 FAQ ·Windows Home ·Office Home
AuthorAll Replies


JohnInSJ
Premium
join:2003-09-22
San Jose, CA
Reviews:
·PHONE POWER
·Comcast

reply to Mele20

Re: [WIN8] User Profiles Service leaked registry handles?

You really don't read what I post, do you.

Nothing changed since XP - apps can and do exit with open registry handles. In XP, you needed to install a 3rd party app to clean those up. Since Vista, Windows does this for you. The 3rd party app didn't long a warning when it did it. Vista and newer Windows does.

This isn't a big deal. Everything is working as it should.
--
My place : »www.schettino.us


plencnerb
Premium
join:2000-09-25
Elgin, IL
kudos:2

For what its worth, I understand what you are saying. Microsoft now has its own process in place to perform the functions that UPHClean did under Windows XP.

That is all fine and good, as the end user does not have to go figure out how to get that 3rd party app, and install it. Windows now does it.

But, I guess what still bugs me, and I think Mele20 See Profile as well, is that the processes that are not closing down properly are Microsoft's own processes. In her case, she has many references to lsass.exe , and in my case, as well as sekim See Profile's, the process is svchost.exe . You would think out of all the applications, the OS would be coded to not cause this problem!

I think that is why we're getting frustrated with this. If the app was some third party to begin with (like a Virus Scanner for example), while it would probably still be a frustration to see the warnings, we could put the blame on said application. But, that's not the case, as the processes that are showing up in these warnings are part of the OS, which was written by Microsoft.

What gets me is that in my case, it appears that something is trying to uninstall every time. Sure, I can see that showing up once or twice, but on every boot? What is Windows trying to remove every time I reboot? Not to mention, in my case specifically, this is an issue with Windows 8. On the exact same hardware (sans the hard drive), when I'm running Windows 7, I get a "clean" log on every boot; meaning, if I clear the logs and then reboot, once the system is up, I will have zero critical events, zero error events, and zero warnings. Just a lot of informational and security events. So I know that there was no issues with the shutdown or startup of my system. Life is good.

I get that the new functionally of Windows Vista, 7 and 8 is doing its job, and that's all find and great. However, it just seems like bad coding on Microsoft's part. If they cannot do this right, how can they expect other software developers to do it right either.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail


Sunday, 26-May 01:39:33 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics