Issue 1021 on fresh install

Hello,

I recently purchased a new laptop and did a fresh windows install on another. After doing all windows updates and downloading the game, both computers can not log into the game. It hangs at “Connecting to Blizzard server” and eventually gives error code 1021. I have done the recommended steps with my router (kept it unplugged completely for 4 hours) and still have the issue.

As a side note, I have an older PC that I hadn’t used in a while and it is able to load the game just fine.

So the issue is only on the 2 laptops that did a fresh Windows and Diablo install.

Any suggestions?

Here is my DxDiag , the full one is too big to post. I also noticed I have the same error in SC2:

------------------
System Information
------------------
      Time of this report: 2/15/2020, 14:14:04
             Machine name: MSI
               Machine Id: {0E0616EC-17BE-4B2E-B2FA-58C30C71207E}
         Operating System: Windows 10 Home 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202)
                 Language: English (Regional Setting: English)
      System Manufacturer: Micro-Star International Co., Ltd.
             System Model: GS60 6QD
                     BIOS: E16H8IMS.10C (type: UEFI)
                Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz
                   Memory: 16384MB RAM
      Available OS Memory: 16294MB RAM
                Page File: 5767MB used, 12958MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 120 DPI (125 percent)
       System DPI Setting: 120 DPI (125 percent)
          DWM DPI Scaling: UnKnown
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
 DirectX Database Version: 1.1.3
           DxDiag Version: 10.00.18362.0387 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
      Display Tab 2: No problems found.
        Sound Tab 1: No problems found.
          Input Tab: No problems found.


Problem signature:
P1: Diablo III64.exe
P2: 2.6.7.64706
P3: 10.0.18362.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER6 +++:
Fault bucket 1270333062791350936, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: SC2_x64.exe
P2: 4.11.3.12125
P3: 10.0.18362.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER7 +++:
Fault bucket 1200753357410593384, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Hey, cybrwlf! Thanks for including details here. I’m not too concerned with what we have on the DxDiag, though incomplete. There was common language runtime error and radar preleaks, but it typically shouldn’t cause this behavior.

The 1021 error is typically tied to a connection issue and with this happening with 2 of the 3 devices on the home network here, it sounds a bit like there may be a common connection or network issue.

Could you try an alternative connection to see if this works for one of the laptops? While not supported, a VPN is another option. While this won’t eliminate the home network as a concern, it should reroute the connection and change the DNS.

If either helps or neither can be done, trying another DNS provider like Google DNS or Cloudflare may be some alternatives to try.

If it persists, let’s gather a WinMTR test while attempting to connect for 5 to 10 minutes. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~