MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Yakumo replied to Bilar Crais's topic in vLiteYou can achieve this without rebooting or safe mode, and without altering any file or folder privileges by : in service manager stop Windows Management Instrumentation Service, it will also stop it's dependencies Security Center, and IP Helper in administrator elevated command prompt (left hit win key to open start menu search, type cmd then ctrl+left shift and press enter) use an admin accounts log in details : this will start a cmd shell with full admin privileges. using that : c: cd \ md backupres cd \ cd windows\system32\wbem\repository move * c:\backupres exit service manager start first Windows Management Instrumentation Service and then Security Center, and IP Helper. you may wish to use computer manager -> Services and Applications -> WMI Control right click it, select properties, use the Backup and restore tab to create a repository backup to resolve this issue quicker if it happens again. using this method I have not had any problems with MS DTC, though that may be entirely coincidental.
Yakumo replied to Bilar Crais's topic in vLiteI've started to get it too, I've had 2 total system freezes this week on a _very_ clean v64u system (with sp1 and all windows updates except the language packs) which has been flawless for months. Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. I'll try the fixes above shortly, thanks. I hope MS get wind of this and look into it as I've seen a few posts about it, and the only thing on MS's site seems to be how to stop the error being added to the log rather than how to fix the actual problem http://support.microsoft.com/kb/950375/en-us/