[Help] Ethernet no longer works after installing Fences 2

Use system restore to a time before installing fences.If it was successful i'd run hard drive diagnostics,file scan first then a sector scan & a virus scan afterwards,unless win 10 was an upgrade then your on your own.

other options before doing system restore:

do a hard drive file scan first,it's a 3 step process & is quite quick.right click on drive C,select properties,tools tab,error checking & check now button,should be a tick in the first box after hitting check now so start it

reboot after scan finished not before checking log

failing that

start support ticket

device manager may have info on network device or check event viewer

can't help much else as it really doesn't make sense as to why fences would have an effect,i suspect there's other issues at play.My rule of thumb is "you can't install yet more software on an already buggy computer".Well that's where i'd start & slowly work backwards to try to determine where the issue lies.As for my upgrade comment most suggest fresh install as you just don't know what balls up windows install did..lol..

lastly did you

https://www.youtube.com/watch?v=nn2FB1P_Mn8

That will be coincidental.  Fences will have no affect on an Ethernet connection.

However.....

Windows 10 is 'famous' for dropping connections.  It is likely a Windows Update has been the cause.

Really.... I've installed it on dozens of systems and have not seen that.

Do tell...

 blakey113

Try checking for a driver update for your NIC.

https://www.google.com.au/?gws_rd=ssl#q=windows+10+drops+wireless+connection

Ditto.

I guess we're the lucky ones, Buff. So far, I have had pretty much zero problems with Windows10. I use it as my main OS on 5 rigs.

Thing is, guys, it's not just Blakey's ethernet that's been affected.  There's also the firewall and diagnostics gone down. 

I do have to agree with Jafo, though, that Objectdock is unlikely to be the cause.

It is more likely to be Windows Updadte causing these issues, and a roll-back may well resolve them.

An investigation into which update is the culprit is wise, however, so it can be hidden from future 'manual' installations.... if Win 10 allows WU to be reset from the default auto-install, that is.

That's another reason I don't like Win 10...  enforced updates... which will also come into effect for Pro and Enterprise editions in the not so distant future. 

I would argue that it is more likely to be something else on blakey113's machine causing the problem, since I have none of these problems, and apparently no one else has reported these problems.

Windows Updates are automatic on my rigs. No problems at all.

Different systems use different configurations, so, it's hard to say what is the problem. But I doubt that ObjectDock has anything to do with it.

Microsoft has provided a solution to unwanted/unneeded updates.

https://support.microsoft.com/en-us/kb/3073930 

Step 1 – First things first, Right-Click the newly-reinstated Start Menu and select Command Prompt (Admin) from the drop-down menu.

Step 2 – Type out the following command, then hit the Enter key 

reg delete HKCRCLSID{988248f3-a1ad-49bf-9170-676cbbc36ba3} /va /f

Step 3 – Enter the below command into the Command Prompt and then triumphantly hit the Enter key

netcfg -v -u dni_dne

Step 4 – Restart the PC and then double-check your wifi settings. You should now see a revived list of all of the available networks within range.

That may be the case, some software/driver configuration on his machine, but it may still have been a Windows update that triggered the issues.  Back before I began manually installing Windows updates, I had an issue where I could not drag and drop, open various files and folders with my cursor, among other things, and there was nothing in MS' knowledge base regarding my particular issue, so I did a system restore and manually installed each update until I found the culprit.... which I hid from future installations.  Essentially, it was something peculiar to that particular machine. .  The same update, however, installed on 3 other machines I have without issue.

In some respects, that's like closing the stable door after the horse has bolted.... creating a fix for after an update has borked somebody's machine.  While MS may take every precaution not to mess up poeple's machines, enforced updates is not something I'd want, given the experience above.  By manually installing each update individually I can see instantly if one is problematic and, if so, I simply uninstall it and hide it from future downloads... without all that diagnostic work to find the cause.