Also I've tried "netsh winsock reset" as an admin in powershell and reset. No change.
I've noticed if I go into the Windows troubleshooting it finds, "One or more network protocols are missing on this computer" and proceeds to "fix" it. It changes the status to "Fixed" but the internet still doesn't work. If I run the troubleshooter again I go through the same process.
Things are getting weird.
Last edited by Blender99; 23 Mar 2016 at 20:08.
Since this is for a wireless network, you might see if deleting it and setting it back up from scratch may help.
I did
settings>update and security>recovery
Rolled back to the previous build. It undid what the In-place upgrade messed up. Now I'm just facing the original issues I had which I'll fix with a new profile. Brink thanks for helping, I appreciate it.
can this fix my overheating problem when i upgrade to win 10 ?
Hello Blitzhartwright,
Most likely not. Overheating is usually caused by improper air flow (ex: dust or covered vents), overclocking, or driver or hardware issues.
Please continue this in your original thread below. Hopefully you'll get a solution soon. :)
is there solution for "fan running at fullspeed" after upgrading ?
Will doing one of these options fix my problem?
I had lost Cortana functionality, which lead me to try a Powershell script to restore it. It did, but then I was getting errors trying to open photos and videos. The error was "The remote procedure call failed". I could see in Default Apps in Settings that they were all set to "TWINUI".maybe it affected these other apps. Or maybe they were affected along with Cortana, and I didn't notice.
I tried running some more Powershell scripts to "repair" the apps, but to no avail. Now Calculator and Windows App Store are not working either. They all appear under "Other" in the "All Apps" list as "@{Microsoft.Windows.Store_2015...}" etc.
Would this procedure (planning to use the MCT to create a DVD?) fix my problems? Or is there something less drastic I could try? Unfortunately I didn't have System Restore running at that point - only noticed it wasn't active after the problem occurred (of course!)
Quote
