I'm Stumped
Results 1 to 8 of 8

Thread: I'm Stumped

Threaded View

  1. #1
    Join Date
    Aug 2001
    Location
    Tenn., USA
    Posts
    356

    I'm Stumped

    I am stumped. I have just re-installed XP Pro, which came bundled w/ SP1. I have the security updates CD which includes XP SP2 and other critical fixes. I am unable to install, getting the error "The automated page did not start properly. You must log on to your computer with administrator privileges to use this automated page. If you are already logged on as a computer administrator, try pressing F5 to refresh your browser."
    I am currently logged on as administrator, and have had no problems logging on as administrator, or no other problems that I am aware of with the administrator acc't. I created a second admin acc't, still could not get past this error, so I deleted the duplicate admin acc't. I have browsed the CD and installed what I could manually--KB823182, KB824105, KB825119, KB826939, KB828035, Q819696, and SP1a is also indicated as installed.
    Relevant event viewer info:A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Source:WinMgmt, event ID:63.

    Support center info:
    Explanation:The Windows Management Instrumentation (WMI) provider subsystem runs individual providers within specific COM servers based on their required security level. Only administrators are allowed to register providers and configure their required security level, and only trusted providers should be configured to use LocalSystem. This warning message is an audit record indicating that the provider is running with the privileges of the LocalSystem account.
    User Action :Verify that the provider is trusted and requires the privileges of the LocalSystem account. If the provider is not trusted, change the hosting model to either LocalServiceHost or NetworkServiceHost by changing the HostingModel property of the _Win32Provider instance for the specific provider. To do this, use Cscript to run the following script after modifying the namespace and provider variables to match those reported in the message.
    ' Change the hosting model for a WMI provider
    computer = “.”
    namespace = “root\cimv2”
    provider = “ProviderName”
    const wbemNotFound = &h80041002
    Set objWMIService = GetObject(“winmgmts:\\“ & computer & “\” & namespace)
    Set colSWbemObjectSet = objWMIService.ExecQuery(“select * from __Win32Provider where name = '“ & provider & “'”)
    count = 0
    for each providerObj in colSwbemObjectSet
    wscript.echo “Changing hosting model for provider ” & provider & “ in “ & namespace & ” namespace”
    wscript.echo “Old value: “ & providerObj.HostingModel
    ' Use NetworkServiceHost for providers that need remote access to other machines
    ' Use LocalServiceHost for providers that do not need remote access
    providerObj.HostingModel = “LocalServiceHost”
    providerObj.Put_
    wscript.echo “New value: “ & providerObj.HostingModel
    count = count + 1
    next
    if (count = 0) then
    wscript.echo “Provider “ & provider & “ not found in “ & namespace & “ namespace.”
    end if
    If the provider depends upon the higher privileges of the LocalSystem account, it might not function correctly with the lower privilege. Note that some providers included with Windows require LocalSystem to operate correctly.
    For more information about provider hosting and security, see the MSDN article Provider Hosting and Security.
    Developer Network key info:
    http://msdn.microsoft.com/library/de...d_security.asp
    Windows 2000, Windows NT 4.0, and Windows Me/98/95: Providers are loaded in-process with the Windows Management service (WinMgmt.exe), running under the LocalSystem security account. Failure of a provider causes the entire WMI service to fail. The next request to WMI restarts the service.
    Failure to set a value for HostingModel will generate NT Event log errors 5603 and 5604. A log entry is also made in wbemcore.log.
    wbemcore.log info: (Sun Mar 13 17:57:17 2005.2159265) : Failed to pre-process an instance using a property provider. Error code: 8004100A.
    Googled http://forums.pcw.co.uk/thread.jsp?f...&thread=35064.
    Deleted all files in D:\WINDOWS\system32\wbem\Repository. Rebooted. No Change.

    Backed up registry. verified permissions in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
    No change.

    I know this is a lot of information, but I am stumped and the info at MS Developer website is all Greek to me.
    Last edited by rednek tek; March 16th, 2005 at 12:44 AM.
    "Internet Explorer, You're Fired"

    Ignore the liberal media. They do not report the news but their slanted infotainment version of it, and should be declared enemy combatants for willfully undercutting and sabotaging the ongoing war on terror. It's OK to disagree with the reason for the war, but sabotaging the effort is treason.

    Avatar created by Niels Leenheer

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •