Windows 7 Every time I launch, Chkdsk replaces "invalid security ID" (Dual system Win 7 + Win 10)

  • Thread starter Thread starter Chevrana
  • Start date Start date
C

Chevrana

Intro:

As a compromise I installed Windows 10 to my PC next to Win7 to be able to run applications Win7 isn't capable anymore. I wish to keep 7 as a OS to switch to, whenever necessary. I am aware this will not last/work forever and am prepared that this might be one of the final Win7 constellations I've set up. But as of now Win7 is part of my 'hard coded' working equipment.


Switching between both OS:

I recognized that I needed to switch the OS by toggling "First boot device" via BIOS, so there's no selection of OS like you're used to it when i.e. using different Win7 versions on the same PC. Whyever~However, might not be any news to an expert. I dealt with that by making use of the Gigabytes Motherboard-Tool to switch the "First boot device" to the desired disk with the right OS on it.


The problem spiral so far:

So far so good, running fine for about a month now, until today all of a sudden my planned Windows 7 launch (Have had shutdown in Win10 yesterday and switched the "First boot device" to 7) took a break to do a CHKDSK with every single drive (internally) plugged in my PC, including the Win10 one. At first I was like ... okay let's do this, but as the usual scan went through so far with the first partition, (partition E:) it started to tackle the security ID thing I mentioned within the Headline/Subject, which made me suspicious about what exacly he is doing right now and if this really was what I wanted after all, so I aborted the security ID reset. (complete line name: "Replacing invalid security ID with default security ID [Increasing number-count value here]")


After rebooting and logging into my Win7, I recognized that the partition it was working on shortly after does now have two alterations:

  1. Permission/access conflicts. Which means that I needed to confirm administrator status to be able to enter containing folders, when there never was a need to before. And after getting the permission after some loading time, I got a golden Padlock on it. (I removed it by adding normal "Users" to security tab with full access rights)
  2. And a message about my Trash bin on Drive E: being corrupted and needed to be resetted. (Did confirm to do so, but nothing changed, so I had to reset the trash bin on E: manually with the "rd /s /q E:\$Recycle.bin" order within the command prompt. (This seemed to have worked for this time's boot, as it's not prompting any more when calling the Properties window. But while writing this I didn't restart the PC yet, so it could still turn out to be a positive-false.)



So after all, I need a specialist's point of view here, because at that level I am definitely out of clues.


So what exacly would you do in my case if you would want this dual OS setup to work, without doing a total reset?

I mean yes, the system is still working right now, yet I don't wanna sit on a bomb here. Because even if I manually stop the CHKDSK from checking all of my disks and let it mess up my security rules again, there's still the fact that apparently it thinks my drives are "dirty", despite the fact that it's all been freshly reinstalled 2020. (Win10 even in December 2020)

  • The Virus-question: I didn't have a notable virus impact as well (Using antivirus and from time to time even Malwarebyte's AMW) so where to go from here? I don't wanna ignore the state if it's a correct feedback, but somehow I have the thought that Win7 might just not get along with Windows10 administrating/indexing/interacting with/ect the same drives/files, even if not at the same time.
  • Would it be a solution to stop chkdsk from overwriting the security settings point and do the rest of the tasks as usual to 'fix' the dirty disk status? Is there even a way to prevent chkdsk from messing around with the folder security settings? I really want to have access to my folders from both OS versions after all, without the partitions being dirty/damaged, ect.


Unregular behaviour I witnessed with Windows 7 since Win10 is on board:

  • When running Win7 I'm incapable of rebooting the system without getting a message about 'plugging in a device with an OS on it'. It's a dead end message. But if I turned off the computer then or shut it down properly in first place, win7 booted normally. Before I installed Win10 I didn't have this problem and windows7 always booted normally.


My Hardware/Software setup:

- Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz

- Gigabyte X99-Gaming 5

- NVIDIA GeForce RTX 2080 SUPER

- 32gb RAM

- Win7 Professional 64bit (final) (SSD)

- Windows 10 (updated January 2021) (HDD, temporary)


If there's a diagnosys file you need me to add, please name it.


Thanks in advance,

ChV

Continue reading...
 

Similar threads

Back
Top