Can't connect to this Wi-Fi after updating windows 11 24H2 update

Anonymous
2024-10-09T05:27:51+00:00

In previous version of windows 11 i am using wireless network from router but after updating the window 11 24H2 version i can't connect wireless network from router but i can connect smartphone's wifi and router through LAN cable.

I have done all the troubleshooting steps and update fixer, reset network through settings, deleted cache using command prompt and done all things using with forums or troubleshooting but still issue is not resolved.

If anyone can help then please give me suggestions to how to resolve this issue. I hope windows help center connect & give proper response to getting error fix.

Windows for home | Windows 11 | Windows update

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

88 answers

Sort by: Newest
  1. Anonymous
    2025-03-24T13:53:22+00:00

    I created a detection and remediation script pair for use in Intune to check if the registry-value has changed at boot.

    If it does, it immediately changes the value and reboots - before a user can log in.

    That way, Start 3 stays that way, without jumping to Start 4 and killing the wifi again.

    This works even without admin rights, as I run the script with SYSTEM rights.

    Enjoy.

    ====================================================================================

    remediation.ps1

    $scriptPath = "C:\Scripts\Check-WinHttpStart.ps1"

    Zorg dat de map bestaat

    if (-not (Test-Path "C:\Scripts")) {

    New-Item -Path "C:\Scripts" -ItemType Directory -Force | Out-Null
    

    }

    Maak het control script aan (indien nog niet aanwezig)

    $scriptContent = @'

    $regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc"

    $currentValue = Get-ItemPropertyValue -Path $regPath -Name Start -ErrorAction SilentlyContinue

    if ($currentValue -ne 3) {

    Set-ItemProperty -Path $regPath -Name Start -Value 3
    
    Restart-Computer -Force
    

    }

    '@

    if (-not (Test-Path $scriptPath)) {

    $scriptContent | Set-Content -Path $scriptPath -Encoding UTF8
    

    }

    Verwijder eventueel oude taak

    Unregister-ScheduledTask -TaskName "CheckWinHttpStart" -Confirm:$false -ErrorAction SilentlyContinue

    Maak nieuwe scheduled task aan

    $action = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-ExecutionPolicy Bypass -WindowStyle Hidden -File "$scriptPath""

    $trigger = New-ScheduledTaskTrigger -AtStartup

    $principal = New-ScheduledTaskPrincipal -UserId "SYSTEM" -RunLevel Highest

    Register-ScheduledTask -TaskName "CheckWinHttpStart" -Action $action -Trigger $trigger -Principal $principal -Settings (New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -StartWhenAvailable -DontStopIfGoingOnBatteries -Hidden -DisallowStartOnRemoteAppSession) -Force

    =================================================

    detection.ps1

    if (Test-Path "C:\Scripts\Check-WinHttpStart.ps1") {

    Write-Host "Script aanwezig"
    
    exit 0
    

    } else {

    Write-Host "Script ontbreekt"
    
    exit 1
    

    }

    =================================================

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-03-11T06:17:23+00:00

    after 2 or 3 days we face the same issue is there any permanent resolution ???

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-07T21:44:06+00:00

    Use Network Reset on Windows.

    Type to Search "Network Reset"

    You'll need local admin.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-03-04T11:05:36+00:00

    Hi everyone,

    We faced this issue since October, and we managed to finally resolve it just now.

    However, I have to note that our issue was a corporate related (not user with home internet), where the issue was with our DHCP record.

    Find below Microsoft's solutions:

    "Hope all is well. Please let us know if you received a response after contacting with your internal network team to suggest removing the invalid DHCP OPT 43 for scopes that are tentatively contacted by clients under the WLAN connection deployment. As it has been internally documented, the lack of consistent attributes within the payload of DHCP OPT causes that Windows 11 devices simply drop the DHCP Offer, rather than processing the DHCP Request as earlier Windows 10 devices would do."

    Honestly, I think I have seen this resolution somewhere, but I am not a network person. Not sure if this will help home users as well or not.

    Hope it helps anyone.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-02-28T07:26:03+00:00

    thats why i hate when it updates on its own, fml... no fix and people been having this problem since october ****

    Was this answer helpful?

    0 comments No comments