Why would multiple reboots make sense? I can accept three reboots triggering some condition that tries three times before it stops trying, but fifteen?

With my experience dating back to 286 machines, sometimes even kicking the box (literally) solves the problem

Put on yer “re-bootin’” boots !

They don't call them reboots for nothing.

Ahaha what nice memories you brought back!

Have you tried turning it off and on and off and on again?

It sounds like a race condition; you want the CrowdStrike updater to start and pull down the fix before the affected virus definition file is loaded and kills the box.

If you keep rebooting, you eventually may get those to load in the right order.

Sounds a lot like my work laptop's antivirus software, which gives me a total of two minutes of internet from within WSL2 before blocking it entirely.

I'm curious if you are sure it's antivirus? WSL networking is weird and can be a pain in the ass. Especially in VPNs are used.

I'm wondering if you know wsl-vpnkit?

Not familiar with this tool, sorry.

Anyway, had that confirmed by whoever is in charge of security and whatnot, as we have an internal StackOverflow clone and someone asking the same question was pointed to a PowerPoint presentation of dos and don'ts.

I see. For me it was worse with WSL1, where all file operations were scanned by slow enterprise DLP software.

Now with WSL2 most pains I see are related to broken routing when also using VPNs on host. That is where that vpnkit tool shines.

I've found disabling/enabling the virtual network bridge fixes VPN issues.

Of course in win11 Microsoft decided to make the bridge hidden for some unknown reason, so good luck figuring it out...

That's what I thought - it would have to be something probabilistic with a 99% chance within 15 reboots or so.