Looks like code search isn't working in @AzureDevOps . The REST API is returning 0 or few results for things that are obviously present in projects across the org. (e.g. "ext:cs" returns 10 results when we have hundreds)
Log out of the faulty machine but DO NOT STOP it in hyperv manager. Leave it running. Then go back to the cloud shell and run: `az vm repair restore -n faulty_vm -g faulty-rg --verbose` . Verify that the faulty_vm is no longer faulty.
If HyperV still shows the faulty machine is blue screening, boot it into safe mode. Once you can log into the faulty machine, open a cmd prompt to c:\windows\system32\drivers\crowdstrike and delete *C-00000291-00000000-00000059.sys*
If you're having issues with @Azure services and using @CiscoUmbrella, https://t.co/k2lmJ5e5fA shows some domains incorrectly classified/blocked (servicebus/storage). Manifests as TLS errors or SocketExceptions. Add the domains to your Umbrella allow list as a workaround.
@shanselman What brand of filament? And PLA or PETG? I had this issue with my Prusa mini when using Hatchbox PLA filament (never could figure out why). Prusament filament works totally fine though.
@AzureSupport Getting a CORS error when trying to navigate to the Service Health blade: "Access to XMLHttpRequest at 'https://t.co/v0O2EieXC5' from origin 'https://t.co/p9F2ZeAcwS' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present..."
@sand_head Isn't that how the original OG King's Quest PC game was? If you missed one thing at the very beginning, you would only find out hours later that it's impossible to finish the game.
@surenna_p He was talking about the head of his department being an uninspiring teacher who was some hack from MIT who did nuclear physics. Frickin amateur hour amirite