I also have lots of issues after june 11 update.

Cannot even restart pc without turning off power manually.

Wifi adapter gets disabled. Service restarting does not work. Wifi works for a short while after restart.

Utterly messed up.

Also, when i uninstall the updat, windows reinstalls the broken update, ****!!!!!!!!!!!

2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5060842)
Successfully installed on ‎11.‎06.‎2025

That is weird, It could be different issue as well, If not check the reg values again sometimes system repair like sfc or dism repairs re-write all the values that we changed. In the same location Look for Reg Folder called WinHttpAutoProxySvc Location - Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc - Go to Start - and change the value from 4 (disabled) to 3 (Manual) and reboot.

Wifi adaptor should reset now during the boot. Now the issue I faced in my org that gpo rewrites this value to 4 every time so either you run a startup script that changes to 3 everytime or do a tweak a gpo level.

This worked for me for a few day, but now I'm back to having the same issue

Just today my wifi connection disappeared on my laptop. Last time it happened I simply rebooted and that fixed it; didn't work this time. Laptop went to sleep, usually upon waking wifi will take a few seconds to connect, but this time no dice. Checked settings -> updates & found a pending windows (10) system update. Fortunately, I have an ethernet cable, so connected it to my laptop, downloaded/installed the update, clicked "restart," & when finished went to wifi settings to check available networks, found both my networks (2.4 GHz & 5 GHz), clicked/checked both to connect, and viola wifi access was back.

Never had this happen before. My cell was still connected to wifi so was able to check availability troubleshoots, but they looked a bit too complicated for my comfort. I was fortunate applying system update fixed my issue. Maybe this might help someone else, hopefully.

We've had this issue in a corporate environment across a range of customers, it's a regkey. Easy enough to fix: effectively, this registry key gets changed to '4' which disables WinHttpAutoProxySvc as a service, killing the wifi and making it not appear in the GUI. When you enable the network adapter, it turns off immediately - because the service can't run.

You can do this via the GUI as well, just open regedit and then go to HKLM:\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc where you ought to find 'Start' and change that to 3. Tactical restart, should do it.

$ServiceName = "WinHttpAutoProxySvc"
$RegPath = "HKLM:\SYSTEM\CurrentControlSet\Services$ServiceName"
$RegName = "Start"
$DesiredValue = 3
$LogFile = "C:\Tech\service_log.txt"

Function Write-Log {
    param ([string]$Message)
    $TimeStamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
    "$TimeStamp - $Message" | Out-File -Append -FilePath $LogFile
}

Start logging

Write-Log "Script started."

Get the current registry value

$CurrentValue = Get-ItemProperty -Path $RegPath -Name $RegName -ErrorAction SilentlyContinue

if ($CurrentValue -and $CurrentValue.$RegName -ne $DesiredValue) {
    Write-Log "Updating registry value from $($CurrentValue.$RegName) to $DesiredValue."
    Set-ItemProperty -Path $RegPath -Name $RegName -Value $DesiredValue
    Write-Log "Registry key updated successfully."
} elseif ($CurrentValue -and $CurrentValue.$RegName -eq $DesiredValue) {
    Write-Log "Registry key is already set correctly ($DesiredValue)."
} else {
    Write-Log "Registry key not found or inaccessible."
}

Get the current service status

$ServiceStatus = Get-Service -Name $ServiceName

if ($ServiceStatus.StartType -ne "Manual") {
    Write-Log "Service is not set to autostart. Enabling it..."
    Set-Service -Name WinHttpAutoProxySvc -StartupType Manual
    Write-Log "Service enabled. A reboot may be required."
} else {
    Write-Log "Service is already set to autostart."
}

Write-Log "Script execution completed."
Write-Host "Script completed. Log saved to $LogFile"

**

We logged a ticket with Microsoft and they said we had to open a paid-ticket, a good blog on this is as follows: https://www.windowslatest.com/2024/10/27/windows-11-24h2-issues-break-internet-wi-fi-network-sharing-cause-more-bsods/