gaurhoth Posted October 15, 2007 Report Share Posted October 15, 2007 Unfortunately, I've been unable to install Powergadgets on several laptops that I've tried. These are new OS builds with no previous versions of Powershell or Powergadgets. When I try to install Powergadgets, I get a the Please Wait - Initializing Script Files for a few seconds and then I get: "PowerGadgets Creator Installation has encountered a problem and needs to close. We are sorry for the inconvenience." Using the debug option, I get the following additional information: " An unhandled exception of type 'System.Management.ManagementException' occurred in System.Management.dll. Additional information: Provider load failure " As mentioned, this has been tried on several different laptops (altho all the same model Dell D620's) with Windows XP SP2 and all of the latest available patches. I welcome any ideas. Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted October 16, 2007 Report Share Posted October 16, 2007 Googled for "Provider load failure", and it seems to all be related to WMI issues. Can you check to make sure the WMI service is running? Quote Link to comment Share on other sites More sharing options...
TheGadgetGuy Posted October 16, 2007 Report Share Posted October 16, 2007 Hello: Please try running the PowerGadgets installer with the /n switch. To do this, simply open a cmd prompt (PowerShell or not) and run the PowerGadgetsCreator.exe /n Hope this helps Quote Link to comment Share on other sites More sharing options...
gaurhoth Posted October 16, 2007 Author Report Share Posted October 16, 2007 Yes, the WMI service is running and working on the PC. I can make any get-wmiobject call to my local PC that I can think of using powershell. Not sure what Class the install script is trying to access - so I can't really diagnose further. Quote Link to comment Share on other sites More sharing options...
gaurhoth Posted October 16, 2007 Author Report Share Posted October 16, 2007 That seems to have allowed it to install. I'm assuming that bypassed 'something' that was triggering a WMI call? Will tinker and let you know if anything seems 'amiss' - but for now. Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.