Windows 10: microsoft support

why is it that when you ask a question like "windows 10 network error 0x00028001" you get stuff from windows 7, stuff about printers, stuff about everything except what is asked? why is it when you try to research the source of an error that you can not get a direct answer to the problem? i realize that with many different systems out there that there could be different causes but why tell me about different errors that make no mention of the one i asked for or editions of windows i did not ask about or devices that are not related to the problem? why can you not get information on page one of the results? can any one tell me what these errors mean and where i can find solutions that pertain to that issue? theses are all network connection errors 0x00028001, 0x00028003, 0x00020000, 0x00000205.

:)

 

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.