Oct 27 2020 10:32 AM - edited Oct 27 2020 10:37 AM
Hi,
I have noticed that sfc /scannow corrected system files. I wonder. So I tested again on a clean Windows 10 20H2 installation and run directly after sfc /scannow.
Preparation for testing (using VMware is just an example for easy reproducing. You could also use a host system):
Installation:
After successful start, I started directly cmd.exe with administrator privilegs and run sfc /scannow.
It will found corrupted systems files.
What is the Log reporting and why a clean installation is doing so?
I repeated the steps with de_windows_10_business_editions_version_20h2_x64_dvd_ce126f3b.iso (md5: 35df62707e53c2064641ccd5b91acb8d)
Type license: Enterprise
After repeating the steps above, the result is the same.
Regards
Oct 30 2020 12:49 AM
Hello @Morku,
I really appreciate your investigation on this issue. I recommend you to report the problem via Feedback hub, so that it gets addressed by the correct team.
Regards.
Oct 30 2020 03:42 AM
thank you for the advise. So I created now: https://aka.ms/AAa48go
But was unsure about the correct categorie.
I thought reporting in this community will be enough, because I don't like the way over Feedback Hub, since I have to enable Diagnostic data. There is even a character limit?
Hope it will help.
Regards
Oct 30 2020 04:14 AM
@Morku, yes, I believe there is character limit of 1000 but you can attach log files or more characters in .txt file.
Regards.