No Network Adapters after Windows 10 Upgrade

I upgraded a few machines to Windows 10. I used a preview and didn't mind it, so thought I'd take the plunge. All had gone well enough until I upgraded a machine and then had no network adapters. I assumed drivers were needed, but everything looked good under device manager. I updated them with drivers from Lenovo anyway. Still nothing...no wireless or wired adapter visible.

I googled and found this, which looked promising: Fix No Wi-Fi Available After Windows 10 Upgrade Issue, Here’s How

I followed the steps and the first one seemed to take, but the second definitely didn't, and the problem remained.

Then I saw this discussion: Network Adapter missing after automatic windows 10 update

...near the bottom, someone mentions that they had to locate the key in regedit and delete it there, as opposed to doing it through elevated cmd. I tried that way and it worked. THEN I ran the second command from the first link and it succeeded and immediately fixed the issue. I restarted just in case.

I can't add a screenshot since I already did it, but you can browse to and expand HKEY_CLASSES_ROOT>CLSID, then delete the 988248f3-a1ad-49bf-9170-676cbbc36ba3 key and subkeys. Back up your registry first to be safe. Searching for '988248f3-a1ad-49bf-9170-676cbbc36ba3' may be faster if you can copy and paste. Good luck!

Fix: The dependency service or group failed to start // found new hardware

Short post.

I had a problem with a client's machine that suddenly failed to connect to his wireless network. Tried phone support/advice: I knew his machine...probably, his network adapter went down. Recommended he get USB adapter.

No help.

I went to visit. Installed USB wireless adapter. Still can't connect. On login, new hardware found (not related to new wireless device). Disabled old, presumed non-working, adapter. Still finding new hardware and failing to get drivers. Strange.

On mouseover of system tray network icon, "The dependency service or group failed to start" is displayed.

Google it.

A few forums had some fixes...none seemed to work. Even tried (from elevated command prompt) "netsh winsock reset" a couple of times. No help.

Finally found a forum comment that helped (http://forums.techarena.in/networking-security/1038559.htm#post5050766):

[from elevated command prompt -- type 'cmd' in start menu search, right-click and 'run as administrator']

1) netsh winsock reset
2) netsh int ip reset
3) net localgroup administrators localservice /add
4) net localgroup administrators networkservice /add
5) exit
Then reboot.

I'm sure you could have found this otherwise...but I hope more links to it/posts about it with the fix that worked for me can only help, right?

nc

Project Elite v6.5 - Choppy Video Recording and Playback

The Problem

I got an OG Droid (Motorola Droid 1) and have been using it as music player / nerd toy until I activate it when my Verizon contract is up in a few months. At some point after flashing it with the Project Elite v6.5 rom, my video started recording choppy (choppily?). Hence, playing back choppy (due to recording state)...not horribly, but enough to degrade the viewing experience, certainly.

The Fix

A few forums I found said to 'clock cpu to 600MHz'...from what I can tell, they meant to change the following:

Settings > Elite Settings > Performance > CPU settings > Max CPU frequency -- change this to 600MHz

Using the default Kernel, I wasn't able to do this. I first had to modify the kernel by doing the following:

Settings > Elite Settings > Performance > Change Kernels -- from P.E LV 1.05ghz(default) to Elite Series v3 LV 900mhz

Once that is done, I had to restart. Once the kernel was updated, I had to go back and set the Max CPU frequency to 800MHz or 600MHz...either seemed to do the trick for me.

I also made sure I checked the box at the bottom of the 'CPU settings' screen...it seems to 'remember' the clock you set on restart. Which is important.

In Conclusion

This information was available in forums, but wasn't very specific..so I hope to save someone a little time by reading it here.