2008 Startup Manager Damages Services on Vista

tullik

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

tullik

twil wrote
... I did some more investigation. When I go into "services" in Vista and try to start the Windows Event Log manually, I believe I am getting a different error message than before:

Error 4201: The instance name passed was not recognized as valid by a WMI data provider.

Now, this is way out of my league...but searching the net, I find that this seems to be related to either Action Control Lists (ACL's) "corruption" and/or missing in the registry...

FYI -- In case anyone missed it, the problem twil is experiencing is likely not the one caused by PT2008 Startup Manager in all versions before 1.8.0.446.

Please join me in hoping he can recover his Eventlog service without a Vista rebuild ...

twil

Thanks Tullik. I am on a business trip, but will follow your suggestions to see if it helps.

I do have a restore point from before SP1 installation. I was reluctant to restore to this point while running SP1. I tried to uninstall SP1, but that failed. Basically, I was trying to go "backwards" in sequence to get myself to a point approx. matching the restore point (if that makes sense).

I will certainly list any fix that works or my findings, as others may face a similar issue.

Thanks again for help anyone has/would provide...much appreciated.

kracor

Another small item that may help in this area. I only run Windows XP Pro SP2, but this evening I ran a Registry Clean and it came up with over 4,000 registry errors on a comparitively clean installation. Most of the registry entries were for Microsoft Office. Needless to say, I was a bit sceptical about deleting anything, but I was chasing an issue and deleted everything anyway. After the registry was 'cleaned up', I attempted to install my defragmentation program, Diskeeper, and was told that I needed to insure that I had sufficient privileges to start services. I looked in the Services and the Alerter had been disabled. After setting the Alerter to Automatic, I was able to install the software and it's now running it's little heart out. Perhaps the Services issues that folks in Vista are seeing are tied to this same Service being required to run. Worth a look-see.

twil

Thanks again Tullik. Just returned, downloaded your "merge entries", and kicked off my backups. While waiting, I came across another post on the net on this topic...a lot of discussion and potential solutions. I tried a "fix" that seemed to work for a number of people, which was to simply delete folder /windows/system32/LogFiles/WMI/RtBackup and reboot (I renamed it...). Once this was done, I was able to run the Event Viewer again (as well as the task manager).

Lucked out!!!

If anyone is interested in the link to the solution debate:

http://forums.microsoft.com/msdn/showpost.aspx?postid=1280359&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=3

Thanks Again!

pidmojim

Is there a discussion with respect to XP? I can find nothing, but I am experiencing a similar failure of Event Log with XP Pro SP3. I used the debug mode in 468 which yielded one registry entry, but no cure. I have been chasing this for more than three days now and can find no solution. Will uninstalling JV16 cure the problem or will I have to do a recovery install?

jv16

The bug shouldn't affect XP, and uninstalling PowerTools does not help.

But since the problem was located, later versions of PowerTools come with a fix: Simply open the main window of PowerTools, press down CTRL and SHIFT. A new menu called "DEBUG" shows to the main window's top menu, from that menu select "Fix Service Damage Caused By Startup Manager" and the program automatically fixes the problem. If this helps, then the bug also seems to affect some XP systems.

« Previous Page