[Windows Repair] Some verified repairs to add

[neroilo]

I reproduced and solved a couple of bugs in Windows 8.1 Pro x86.
Can you consider to add these fixes in your repair program, please?

1) http://www.eightforums.com/performance-maintenance/62829-event-id-513-capi-2-errors.html

Post #3 and #4 helped me to fix it.

2) https://social.technet.microsoft.com/Forums/windows/en-US/d1ff28fb-a16c-4d12-a717-c43f7a9a34fc/cannot-view-static-ip-address-info-in-tcp-properties?forum=w8itpronetworking

Solution:

We finally got Microsoft to help and they tracked down the problem.
They found a corrupted registry entry in our TCP-IP configuration that doesn't allow the GUI to successfully change the TCP-IP settings.
The reg entry is removed, and the computer restarted.
TCP-IP service finds the reg entry missing, and rebuilds it.
Voila - The GUI displays properly and will set/reset the TCP-IP setting properly.
Unfortunately, I can't tell you what was the original cause of the corrupted reg entry.

Deleting the following reg entry solved our problem:
My computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config

Original source (it worked for other users too):
http://www.pcreview.co.uk/threads/static-ip-changes-to-dynamic-automatically.3904651/

[Shane]

I am always open to adding new things

I just have to see if there is any side effects to deleting that key, such as when I user has a static IP or something like that, but if there is no side effects and Windows Simply rebuilds it then I think it would be good to add to the repair network.

Shane

[neroilo]

I am always open to adding new things

I just have to see if there is any side effects to deleting that key, such as when I user has a static IP or something like that, but if there is no side effects and Windows Simply rebuilds it then I think it would be good to add to the repair network.

Shane

I can confirm my dns settings remained at their place, no need to put them back after removal.

That key represents a sort of network cache easy to break almost like system restore.

Many hours were required just to discover it.

[Shane]

Well removing that key is in some of the repairs MS has on their sites, so I would say that has to be safe, will be real easy to add the one line in to remove it. I will add it to the repair winsock and dns on the next update

Shane

[neroilo]

I will add it to the repair winsock and dns on the next update

Shane

Thank you.

Please consider this too:
http://www.eightforums.com/performance-maintenance/11951-numerous-event-id-10016-errors-win-8-pro-64-bit.html

Cluberti fix in post #5 fixed my event id 10016 errors ... they might be tollerable, but personally I hate that kind of spamming.

[Shane]

Only problem is, part of that repair cant be automated. I havent found a way to change the permissions of a com object the way I do files, registry and services.

I use setacl to do the settings of the permissions,
https://helgeklein.com/setacl/documentation/command-line-version-setacl-exe/

From what I can see it can only do

    Files / Directories
    Registry
    Printers
    Services
    Shares
    WMI

So I am not sure how the com object would be regarded

Shane

[neroilo]

Only problem is, part of that repair cant be automated. I havent found a way to change the permissions of a com object the way I do files, registry and services.

I found some useful stuff here:
http://stackoverflow.com/questions/11363342/change-dcom-config-security-settings-using-powershell

[Shane]

Now that is something to look into.

I am getting ready to move to a new place here in about a week, so I am slammed trying to keep up with stuff and pack. Would you do me a fav and in a couple of weeks give me a reminder about this so I can go play with those commands and see what I can find out?

Shane