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 kommentar(er)
