Main Forum > Tweaking.com Support & Help

WMI repair failed twice , new computer . SOLVED

<< < (2/3) > >>

Boggin:
Magic Jellybean shows you Dell's generic key which will fail to activate a repair install and the product ID is just that.

I have three Toshiba Win 7 laptops (two now upgraded to Win 10) and they all had the same Toshiba generic key.

As Dell have now gone the route of injecting the key into the motherboard as Win 8/8.1 machines have, then a repair install isn't going to be an option and if a sfc /scannow failed to find anything wrong then neither will an offboot one.

What were the WMI Event ID Nos in Event viewer and have you tried a Google search on them as someone somewhere will probably have had the same errors as you at some point in time.

If you click on the error then on Copy/Copy details as text in the lower right pane, you can then right click in the reply box and select Paste.

herb:
I took your advice and searched , i eventually happened upon the below fix , ran it in Command Prompt .  Thanks so much for your help .


 
winmgmt /standalonehost
winmgmt /resetrepository

Boggin:
Glad things have worked out for you.

You can add [SOLVED] to your thread title by going to your first post, click on Modify and type that next to the title.

Willy2:

--- Quote from: herb on January 03, 2017, 08:08:51 pm ---winmgmt /standalonehost
winmgmt /resetrepository

--- End quote ---

To be added to a future version of Windows Repair ? Boggin & Shane ?

Boggin:
I've already emailed Shane about this but have since tried the cmds on one of my laptops.

After the first one I was prompted to stop and start the WMI service to effect.

I ignored that and entered the second cmd where I got a fail error because of the service being in use by others.

I then went into services.msc > stopped WMI and then redid the /resetrepository cmd where it completed successfully.

I then went back into services to restart WMI by clicking on the Start in the top left but it wasn't showing as Started.

It took a reboot to effect that.

As the WMI may be needed by others during the WR, stopping and then starting WMI without a reboot may prove problematic in including it in WR, although the net stop winmgmt and net start winmgmt cmds could be used but (from a Google) the SMS Agent Host or the Firewall may not be auto started.

No doubt Shane should be able to sort that if he ever gets around to reading my email and the shortcut I linked to this thread.

Navigation

[0] Message Index

[#] Next page

[*] Previous page