Windows 10 Win 10 TP bug or just coincidence ?

It's not uncommon to encounter corrupted system files after installing a dual-boot setup, especially with newer operating systems alongside older ones. The changes in the boot loader, system partitions, and interdependencies between different Windows versions can sometimes lead to issues with system files. Here's why this might have occurred: 1. Compatibility: Different versions of Windows have different system file versions. Installing a new Windows version can sometimes affect shared system files used by both versions, leading to corruption. 2. Boot Configuration: Dual-booting involves changes in the boot configuration. This might inadvertently affect the integrity of system files shared between the two operating systems. 3. Automatic Repairs: The System File Checker (sfc) tool might flag these changes, especially if it compares system files with those from the original installation. 4. Repair Process: The Deployment Image Servicing and Management (DISM) tool is helpful in repairing the system image, which could fix any corruptions introduced during the dual-boot setup. In your case, the findings are quite common when setting up dual-boot systems with different versions of Windows. It's a good practice to run tools like sfc and DISM after such installations to ensure the overall stability of both operating systems. If the systems are running smoothly now and both Windows versions are working fine, there's no immediate cause for concern. Regular system file checks and maintenance can help keep both installations in good condition.