This query actually fits into both versions of Windows category but I'll ask it here.
I have Windows 7 Pro on an SSD and a 2nd standard 2TB drive containing data etc. With the end of support looming for Win 7, I bought a 2nd SSD drive. I replaced the Win 7 SSD with the blank new drive, disconnected the video card (because I believe it's not supported) and disconnected the 2TB drive.
I successfully installed Windows 10, reconnected the 2TB drive and proceeded to install a few programs/apps. Because I cannot move straightaway over to Windows 10, I put the Windows 7 SSD back in (together with the 2TB drive) and booted up. For the next 5 hours or so it did a chkdisk and performed hundreds if not thousands of '...replacing invalid security id with default security id for file xxxxx...'.
It (Windows 7) seems to be OK now, but what caused that to happen ?? Whilst running Windows 10 I did create a folder on the 2TB drive and access other files. Did this cause those files to be given different properties which are invalid in Windows 7 ?? Just a thought.
I have Windows 7 Pro on an SSD and a 2nd standard 2TB drive containing data etc. With the end of support looming for Win 7, I bought a 2nd SSD drive. I replaced the Win 7 SSD with the blank new drive, disconnected the video card (because I believe it's not supported) and disconnected the 2TB drive.
I successfully installed Windows 10, reconnected the 2TB drive and proceeded to install a few programs/apps. Because I cannot move straightaway over to Windows 10, I put the Windows 7 SSD back in (together with the 2TB drive) and booted up. For the next 5 hours or so it did a chkdisk and performed hundreds if not thousands of '...replacing invalid security id with default security id for file xxxxx...'.
It (Windows 7) seems to be OK now, but what caused that to happen ?? Whilst running Windows 10 I did create a folder on the 2TB drive and access other files. Did this cause those files to be given different properties which are invalid in Windows 7 ?? Just a thought.
