Share via

The Dreaded Windows 10 Wi-Fi "Default Gateway" Issue yellow triangle Constant Dropout on Hotspot Activation

Anonymous
2019-06-22T00:41:14+00:00

Hi,

I have a problem setting up the mobile hotspot for my laptop without getting the constant Windows 10 Wi-Fi Yellow Triangle of death (as I like to call it now). The issue was never there on Windows 8.1 version

I am sure I am not the only one having this issue and I am pretty sure lots of Windows 10 Users have all seen this usual yellow triangle with exclamation mark on the Wi-Fi indicating no Internet access. (I have went through countless of Microsoft community questions and this seems like a trend, one thing to note it is very common among Intel Wi-Fi driver users).

Once you right click and attempt to fix it using the troubleshooter it resets the Wi-Fi adapter and says something about "The Default Gateway is fixed" with a green check mark 

I have attempted every possible solution I found online by Microsoft and Intel from completely wiping and updating drivers to the latest Wi-Fi Driver, firewall disabling, netsh resets ipconfig resets, sfc scans, manually configuring IPs (disabling DHCP), unchecking power management override to sleep my wifi in setting. I have checked for interference using wifi analyzer, I have checked my router and my other Windows 8.1 Acer laptop runs its hotspot fine without this happening ever.

The only thing I noted once I click "View Detailed information" in the troubleshooter is the driver versions seem to Mismatch for which what the netwb02.inf file is saying vs what is been updated in the Device manager and using the netsh show wlan drivers command.

And below is the complete information from the troubleshooter:

I have tried to check the ETL file with Event Viewer to see what triggers it but it crashes.

Could a well informed person share some opinions on what might be the issue here?

Any further insights would be much appreciated.

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

9 answers

Sort by: Most helpful
  1. Anonymous
    2019-06-24T23:31:39+00:00

    Hi,

    Yes I can connect to internet wi-fi with no hotspot configured

    I have done all that uninstall and recovery options and attempted from scratch but nothing worked.

    However after all this I have identified the issue by trial and error,, it comes down to the wireless signal not being able to penetrate my metal shed where I am attempting to hotspot my laptop from, hence the random "default gateway" dropouts when signal bounces off and interferes with another waves.

    I have tested a 24 hour operation outside the bounds of the shed and no issues so far with my connected device to the laptop even with heavy bandwidth usage.

    Thanks for your help and attempts anyway. Much appreciated.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-06-22T23:12:10+00:00

    Apologies,

    Let me clarify

    On the first instance: I mean once the hotspot is running and caused the error, the yellow triangle error doesn't go away if I turn off the hotspot - unless I run the troubleshooter and fix Wi-Fi first, then re run the hotspot.

    On the second instance: I mean the yellow triangle error never occurs if I don't use any form of hotspot at all to begin with. - Hence eliminating a problem related to the network driver itself when running in normal operation.

    Hope this clears up the confusion.

    The problem first started when I used the Microsoft mobile hotspot on its own. I only later resorted to these third party software to see if it will be any better but it was not.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. franco d'esaro 24,991 Reputation points Volunteer Moderator
    2019-06-25T14:17:59+00:00

    I'm glad you solved it and I thank you for your feedback.

    Environments with the presence of metal structures represent a barrier for the wi-fi signal. These structures greatly attenuate the wi-fi radio signal until it is completely canceled.

    Greetings.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-06-22T21:27:42+00:00

    1. I think Hosted Network is supported in the card.
    2. I never get yellow triangle-ed when not running a mobile hotspot or a hosted network
    3. I have tried to reinstall the drivers from scratch and remove and install the new Intel Pro/Set Wireless software using the below steps (as advised from Intel):
    1. Remove WiFi components
    2. Uninstall driver from Device Manager*. If prompted, choose remove driver.
    3. Remove Intel® PROSet/Wireless Software and Drivers from Programs and Features in the Control Panel.
    4. Remove temporary files
    5. Press Windows* Key + R to open the run box. Type Cleanmgr.exe. Press OK.
    6. Select your boot drive (usually C:\)
    7. Check Temporary Files and uncheck everything else. Press OK.
    8. Remove hidden temporary folders
    9. Go to %USERPROFILE%\AppData\Roaming\
    10. Delete the "Intel" folder found here.
    11. Install the latest version of the Intel® PROSet/Wireless Software and Drivers.
    12. Choose to Customize.
    13. Select all options available.

    Currently I have the latest Wi-Fi Driver 2019 and latest Intel PROSet/Wireless Software and Driver WiFi_20.120.1_PROSet64_Win10.

    I have run by your steps using the troubleshooter

    Step 1) Returned no issues in troubleshooter

    Step 2) I have run the troubleshooter on my Wi-Fi adapter. The troubleshooter restarted my Wi-Fi adapter even though it was working fine and returned the below report:

    Network Adapter Publisher details
    Issues found
    Problem with wireless adapter or access point<br><br><br>Problem with wireless adapter or access point Fixed
    Reset the wireless adapter Completed <br> --- --- <br> Investigate router or access point issues Not run
    Issues found Detection details

    | | 6 | Problem with wireless adapter or access point | Fixed | |<br>| --- | --- | --- | --- | | | | | Reset the wireless adapter | Completed |<br>| --- | --- | |<br>| | Network Diagnostics Log |<br>| | File Name: | 8843F3B2-C09F-42B9-B24B-37115D374BC4.Repair.1.etl |<br>| --- | --- | |<br>| --- | |<br>| --- |<br><br><br><br><br>| | Investigate router or access point issues | Not run |<br>| --- | --- | |<br>| --- |<br>| If you're connected to a hotspot or domain network, contact the network administrator. Otherwise: 1. Unplug or turn off the device. 2. After all the lights on the device are off, wait at least 10 seconds. 3. Turn the device back on<br> or plug it back into the power outlet. To restart a router or access point that has a built-in battery, press and quickly release the Reset button. | | | --- |

    Detection details
    Diagnostics Information (Network Adapter)
    Details about network adapter diagnosis: <br> <br> Network adapter Wi-Fi driver information:<br> <br> Description . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3160<br> Manufacturer . . . . . . . . . : Intel Corporation<br> Provider . . . . . . . . . . . : Microsoft<br> Version . . . . . . . . . . . : 17.15.0.5<br> Inf File Name . . . . . . . . . : C:\WINDOWS\INF\netwbw02.inf<br> Inf File Date . . . . . . . . . : Saturday, September 15, 2018 7:28:15 AM<br> Section Name . . . . . . . . . : Install_MPCIEX_GEN_3160_AC_HMC_WINB_64_AC<br> Hardware ID . . . . . . . . . . : pci\ven_8086&dev_08b3&subsys_00708086<br> Instance Status Flags . . . . . : 0x180200a<br> Device Manager Status Code . . : 0<br> IfType . . . . . . . . . . . . : 71<br> Physical Media Type . . . . . . : 9 <br> ---
    Diagnostics Information (Wireless Connectivity)
    Details about wireless connectivity diagnosis: <br> <br> Information for connection being diagnosed<br> Interface GUID: 8592f331-5f2f-403b-adf2-ce919d0a9522<br> Interface name: Intel(R) Dual Band Wireless-AC 3160<br> Interface type: Native Wi-Fi<br> <br> Connection incident diagnosed<br> Auto Configuration ID: 1<br> Connection ID: 1<br> <br> Connection status summary<br> Connection started at: 2019-06-23 06:25:02-427<br> Profile match: Success<br> Pre-Association: Success<br> Association: Success<br> Security and Authentication: Success<br> <br> List of visible access point(s): 7 item(s) total, 7 item(s) displayed<br> BSSID BSS Type PHY Signal(dB) Chnl/freq SSID<br> -------------------------------------------------------------------------<br> D8-D7-75-08-A8-D8 Infra <unknown> -83 11 OPTUS_08A8D7<br> B0-AC-D2-3C-91-A3 Infra <unknown> -76 4 EXETEL 3C91A3 2.4G<br> 10-0D-7F-E1-D7-62 Infra <unknown> -74 11 OPTUSVD3D4F248<br> FA-8F-CA-3A-DD-A4 Infra <unknown> -71 11 (Unnamed Network)<br> B6-B6-86-98-BE-E1 Infra <unknown> -89 11 DIRECT-E1-HP ENVY 5000 series<br> B0-AC-D2-3C-91-A4 Infra <unknown> -82 5500000 EXETEL 3C91A3 5G<br> 08-02-8E-F0-50-41 Infra <unknown> -85 6 Telstra110C<br> <br> Connection History<br> <br> Information for Auto Configuration ID 1<br> <br> List of visible networks: 8 item(s) total, 8 item(s) displayed<br> BSS Type PHY Security Signal(RSSI) Compatible SSID<br> ------------------------------------------------------------------------------<br> Infra <unknown> Yes 50 Yes OPTUS_08A8D7<br> Infra <unknown> Yes 41 Yes EXETEL 3C91A3 2.4G<br> Infra <unknown> Yes 41 Yes OPTUSVD3D4F248<br> Infra <unknown> No 48 Yes (Unnamed Network)<br> Infra <unknown> Yes 18 Yes DIRECT-E1-HP ENVY 5000 series<br> Infra <unknown> Yes 20 Yes EXETEL 3C91A3 5G<br> Infra <unknown> Yes 30 Yes Telstra110C<br> Infra <unknown> Yes 20 Yes OPTUS_08A8D7_5GHz<br> <br> List of preferred networks: 3 item(s)<br> Profile: OPTUS_7E52B8_5GHz<br> SSID: OPTUS_7E52B8_5GHz<br> SSID length: 17<br> Connection mode: Infra<br> Security: Yes<br> Set by group policy: No<br> Connect even if network is not broadcasting: No<br> Connectable: No<br> Reason: 0x00028002<br> Profile: OPTUS_08A8D7 2<br> SSID: OPTUS_08A8D7<br> SSID length: 12<br> Connection mode: Infra<br> Security: Yes<br> Set by group policy: No<br> Connect even if network is not broadcasting: No<br> Connectable: No<br> Reason: 0x00028001<br> Profile: OPTUS_08A8D7<br> SSID: OPTUS_08A8D7<br> SSID length: 12<br> Connection mode: Infra<br> Security: Yes<br> Set by group policy: No<br> Connect even if network is not broadcasting: No<br> Connectable: Yes<br> <br> Information for Connection ID 1<br> Connection started at: 2019-06-23 06:25:02-427<br> Auto Configuration ID: 1<br> Profile: OPTUS_08A8D7<br> SSID: OPTUS_08A8D7<br> SSID length: 12<br> Connection mode: Infra<br> Security: Yes<br> Pre-Association and Association<br> Connectivity settings provided by hardware manufacturer (IHV): No<br> Security settings provided by hardware manufacturer (IHV): No<br> Profile matches network requirements: Success<br> Pre-association status: Success<br> Association status: Success<br> Last AP: d8-d7-75-08-a8-d8<br> Security and Authentication<br> Configured security type: WPA2-PSK<br> Configured encryption type: CCMP(AES)<br> 802.1X protocol: No<br> Key exchange initiated: Yes<br> Unicast key received: Yes<br> Multicast key received: Yes<br> Number of security packets received: 0<br> Number of security packets sent: 0<br> Security attempt status: Success<br> Connectivity<br> Packet statistics<br> Ndis Rx: 18571<br> Ndis Tx: 21400<br> Unicast decrypt success: 197<br> Multicast decrypt success: 0<br> Unicast decrypt failure: 0<br> Multicast decrypt failure: 0<br> Rx success: 288<br> Rx failure: 0<br> Tx success: 191<br> Tx failure: 0<br> Tx retry: 66<br> Tx multiple retry: 23<br> Tx max lifetime exceeded: 0<br> Tx ACK failure: 112<br> Roaming history: 3 item(s)<br> Times: 2019-06-23 06:39:32-059<br> Roamed from BSSID: d8-d7-75-08-a8-d8<br> Reason: 0x00000002<br> Times: 2019-06-23 06:39:28-897<br> Roamed from BSSID: d8-d7-75-08-a8-d8<br> Reason: 0x00000000<br> Times: 2019-06-23 06:39:27-861<br> Roamed from BSSID: d8-d7-75-08-a8-d8<br> Reason: 0x00000002 <br> ---
    Diagnostics Information (Wireless Connectivity)
    Details about wireless connectivity diagnosis: <br> <br> For complete information about this session see the wireless connectivity information event.<br> <br> Helper Class: Auto Configuration<br> Initialize status: Success<br> <br> Information for connection being diagnosed<br> Interface GUID: 8592f331-5f2f-403b-adf2-ce919d0a9522<br> Interface name: Intel(R) Dual Band Wireless-AC 3160<br> Interface type: Native Wi-Fi<br> <br> Result of diagnosis: There may be problem <br> ---
    Diagnostics Information (Wireless Network Adapter)
    Details about wireless network adapter diagnosis: <br> <br> For complete information about this session see the wireless connectivity information event.<br> <br> Helper Class: Native Wi-Fi MSM<br> Initialize status: Success<br> <br> Information for connection being diagnosed<br> Interface GUID: 8592f331-5f2f-403b-adf2-ce919d0a9522<br> Interface name: Intel(R) Dual Band Wireless-AC 3160<br> Interface type: Native Wi-Fi<br> Profile: OPTUS_08A8D7<br> SSID: OPTUS_08A8D7<br> SSID length: 12<br> Connection mode: Infra<br> Security: Yes<br> Connect even if network is not broadcasting: No<br> <br> Result of diagnosis: Problem found<br> <br> Root cause:<br> This computer is continuously switching between two or more wireless routers or access points<br> <br> Detailed root cause:<br> Excessive roaming (between access points, within a profile or a preferred network)<br> <br> Repair option:<br> Select one preferred network<br> Windows Help and Support can provide more information about how to prevent your computer from continuously switching between wireless routers or access points. <br> ---

    | Network Diagnostics Log | | | File Name: | 8843F3B2-C09F-42B9-B24B-37115D374BC4.Diagnose.0.etl |<br>| --- | --- | | | --- |

    | Other Networking Configuration and Logs | | | File Name: | NetworkConfiguration.cab |<br>| --- | --- | | | --- |

    | Collection information | | Computer Name: | HP-HIMOZ | | --- | --- | | Windows Version: | 10.0 | | --- | --- | | Architecture: | x64 | | --- | --- | | Time: | Sunday, June 23, 2019 6:50:01 AM | | --- | --- |

    Publisher details

    | Windows Network Diagnostics | | Detects problems with network connectivity. | | Package Version: | 4.0 | | --- | --- | | Publisher: | Microsoft Windows | | --- | --- |

    Network Adapter
    Find and fix problems with wireless and other network adapters.

    It is funny to note that the troubleshooter identified the "root cause" as it is trying to jump constantly between two access points even though I am only connect automatically to a single Wi-Fi network which I have double checked more than once now. I have made sure all other saved networks are forgotten except the one I am currently using.

    Step 3) I have attempted the Network Reset below and it reverted all my Wi-Fi drivers to the old ones

    Step 4) Updated Wi-Fi Driver to the latest Intel Dual Band Wireless Adapter AC3160 Properties.

    ...

    After all that the problem still persists.

    I have tried extra steps that I have tried before such as disabling Firewall completely temporarily to check any issues and checking to remove any windows updates that may caused any conflicts (because that is what I think may be happening here)

    I think as a last resort I will backup my personal data and attempt a Fresh Start, it seems a bit radical but I have been struggling with this a while and no solution have worked so far.

    If it does not work after that it is either a hardware issue with the wireless adapter inside the laptop itself (it is a HP ENVY 15 Notebook, a 4-5 years old laptop after all) OR it could be that just there is incompatibility of this feature with an intel card especially with new updates of windows.

    One thing to note is I have tried using the mobile hotspot feature in other Wi-Fi networks before in other places and no matter how good the internet and max signal next to router, it still goes to the yellow triangle of death scenario after a while of using a connected device to the hotspot.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-06-22T09:36:17+00:00

    I have used the Hosted network using netsh commands and third party software (ostoto and connectify) on my Acer laptop which i have updates turned off for (preventing it from going to windows 10) and it works fine.

    And to answer your question: No if I turn off the hotspot i created it does not remove the yellow triangle error. The only solution is to run the troubleshooter to restart the wifi adapter and giving the whole message above.

    As far as the hotspot itself -  it does work but only for a while, the sharing tab has both of these deselected. ( i know of this trick from before when i started hosted network using the cmd prompt ). Now no matter the method i employ in windows 10 for hotspot whether it is the manual creation, windows own "Adhoc" mobile hotspot or third party software the end result is the same, the hotspot works for a while but eventually disconnects the wifi adapter and im forced again to sit on the troubleshooter to get it to reset the wifi driver.

    Even attempting to restart the adapter using cmd commands doesn't do the trick or even disabling it from device manager and then re enabling it again.

    I also noticed that normal browsing from one of my connected devices to the hotspot does not cause the hotspot to give the yellow triangle of death error. Only when heavy bandwidth usage such as downloading updates on my phone or HD streaming it triggers the wifi adapter to turn the yellow triangle error. 

    Now if only windows 10 had that microsoft loopback adapter to auto trigger dhcp to get default gateway back maybe i could find some sort of consolation to automate fixing the error without resorting to sitting on the laptop everytime trying to run the troubleshooter.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments