Happy first week of May! If you didn’t know, this is National Gardening Week (in the UK, at least) and since I’ve been sitting here for forty minutes fishing for a decent analogy - like an old man with a cane pole in a rowboat with. Brand Rep Wrap-Up: April 2023 Spiceworks Originals.Somehow it came down from MS and it wasn’t a Windows Update. The app 100% wasn’t installed in the image. Today all my Windows 11 22h2 Enterprise imaged desktops had Teams auto install itself. The Ultimate Guide to Procmon Opens a new window.Understanding Process Monitor Opens a new window. Given that Quick Assist is based on RDP (Remote Desktop Protocol) I suggest looking in that direction, possibly using Sysinternals/TechNet's Process Monitor Opens a new window ( ProcMon) to look at processes and filtering for FAILURE. So, IMO, the latest Windows 10 Decrapifier script doesn't have anything to do with Quick Assist not working for you. (Note: I never, ever use a Microsoft Account so didn't test this.) Next, I created a Standard local account (the initial account is always added to the Administrators group automatically), started an internet connection then tried to start Quick Assist. It started without issue.Īs a double-check I rebooted so SysPrep could complete, created an initial local account, started an internet connection then tried to start Quick Assist. After completion I started an internet connection and tried to start Quick Assist again. Next I disconnected from the internet and ran in the latest Windows 10 Decraprifier script (albeit with a few additions of my own). I provisioned a test laptop with Windows 10 Pro 20H1 and paused it during OOBE, entered Audit Mode, started an internet connection then tried to start Quick Assist.
0 Comments
Leave a Reply. |