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

}

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

Option 2 Using a Generic Wi-Fi Driver did the trick for me.

2. Use a Generic Wi-Fi Driver
   • Go back to Device Manager, and right-click on your Wi-Fi adapter again.
   • Select Update driver > Browse my computer for drivers > Let me pick from a list.
   • Choose a generic driver like Microsoft Wi-Fi Direct Virtual Adapter or another option listed, and check if it resolves the issue.

OK - I put a comment on the MS Feedback Hub about this problem. Here is the link.

https://aka.ms/AAhdrxh

Derrick - I understand the patience thing. But this happened to me on 1/16/25, it's been happening since Oct. Then an hour ago I read that MS is about to make 24H2 mandatory. I'll try the Feedback Hub thing you mentioned.

When using version 23H2, I did not experience the intermittent Wi-Fi disconnection issues that I encountered with version 24H2. However, I recently purchased a new Galaxy Book5 Pro, which came pre-installed with 24H2. Unfortunately, I faced several software-related issues with this version, so I ultimately reverted back to 24H2.

To share some new information, there was an additional update for 24H2 yesterday. I'm not sure if this update is related to Wi-Fi connectivity, but since applying it, the Wi-Fi disconnection issue seems to have disappeared. That said, I've only been using it for a day, so the reliability of this feedback is not very high yet.