any way to fix the defender using too much cpu? Its scan every file open, on retail windows 11 22000 works fine, but on 22621 slow all the system
next week final release for insiders that is 30 days before public release as always then again something can fail never mind
Lies again ya said this week and nothing just stop cause everyone knows your delusional and about as truthful as saying god is real
i dont notice any slow downs with nvme, windows defender is ok for me even hardened it, for office and credential stealing
I don't see final release happening for insiders, Microsoft hasn't merged the content from Beta branch to Release Preview branch yet
try to install any software, or mount a iso an check task manager. Defender start to use a lot of cpu% and then the software/iso is mounted/installed. On Windows 11 21H2 works fine
If I create an ISO image from UUP dump despite the fact that in the process it gives me everything correct when I do a clean installation when checking with PowerShel using the sfc /scannow command it gives me the following: Windows Resource Protection indicates that it has repaired the files corrupted or damaged installation files. Instead creating the Windows 11 ESD Repository ISO image with esd-decrypter-wimlib-63 I do a clean install run PowerShell sfc /scannow it gives me the following: Windows Resource Protection found no violations. Could someone tell me what this anomaly from one image to the other could be due to? Thanks.
I want to give it a try to this build, however I am still running an old Haswell platform with i7-4790K and 16GB DDR3 RAM on an ASUS H81M-R. I know I can bypass TPM and SecureBoot checks, however, what troubles me are the drivers. The official ASUS page supports only up to Windows 10 (of course), so, even though 11 is 10 under the hood, will the same drivers from Windows 10 be still compatible, working smoothly? I am not usually in the habit to download generic drivers from Windows Update.
Cumulative Update for Windows 11 Insider Preview (10.0.22622.575) (KB5016694) Successfully installed on 8/10/2022