Windows 10: Am I fed up with Microsoft support or what???

I have been in contact with Microsoft support for about a week now and gone through 9 agents and 2 Tiers of support on the chat line to fix problems caused by Windows 10 update. These agents have a nasty habit of starting a procedure and jumping off the chat line before verifying that the problems have been fixed. My computer has been left unusable after one restart and the support agent was not to be found. Even though he has my call back information readily at hand. Call backs have been scheduled but no phone calls have come through. The support line phone number advises that support is going exclusively on a shaky chat line. No person-to-person phone conversations.


This is totally dysfunctional. Can it be that Microsoft, once the jewel of the IS Industry is now just so much slag?

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

B3 Phenom support

I checked gigabyte's site on my GA-M57 and it didn't say anything about b3 stepping update, but all of the x3 chips are b3 steppings, so just use the x3 support bios if available.

 

Microsoft Edge TLS Security

After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.