[JSntgRvr]

No, Windows must boot without pressing F12. That will let me know which is the OS is being detected as the default OS. You can control the boot order in the computer's BIOS
 
In regard to the Windows 7 Installation, there are bad clusters in the hard drive, and that can trigger CHKDSK. Lets perform the following Fix while running Windows 7:

• Highlight the entire content of the quote box below.

Start:: 
CloseProcesses: 
AlternateDataStreams: C:\ProgramData:iSpring Solutions [128] 
AlternateDataStreams: C:\Users\All Users:iSpring Solutions [128] 
AlternateDataStreams: C:\ProgramData\Application Data:iSpring Solutions [128] 
AlternateDataStreams: C:\ProgramData\Reprise:wupeogjxldtlfudivq`qsp`27hfm [0] 
AlternateDataStreams: C:\Users\davids home\Application Data:iSpring Solutions [128] 
AlternateDataStreams: C:\Users\davids home\Cookies:zy8Qj3GUfupn5oVfvajBV [2332] 
AlternateDataStreams: C:\Users\davids home\AppData\Roaming:iSpring Solutions [128] 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:urLyIdmw66pmGCeXdl3Fz9SnrM [2642] 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:WKrGS1tLeTSnx6wwUHcWyvmQN [2166] 
HKLM\...\Run: [] => [X] 
HKLM-x32\...\Run: [] => [X] 
HKU\S-1-5-21-3046525360-976882445-4112316675-1000\...\Run: [] => [X] 
S3 dbx; system32\DRIVERS\dbx.sys [X] 
S3 LVPr2M64; system32\DRIVERS\LVPr2M64.sys [X] 
S3 PID_0928; system32\DRIVERS\LV561V64.SYS [X] 
S3 Synth3dVsc; System32\drivers\synth3dvsc.sys [X] 
S3 tsusbhub; system32\drivers\tsusbhub.sys [X] 
S3 VBoxNetFlt; system32\DRIVERS\VBoxNetFlt.sys [X] 
S3 VGPU; System32\drivers\rdvgkmd.sys [X] 
S3 WN111v2; system32\DRIVERS\WN111v2w7x.sys [X] 
Policies: C:\ProgramData\NTUSER.pol: Restriction <==== ATTENTION 
FolderExtensions: [] -> {F6BF8414-962C-40FE-90F1-B80A7E72DB9A} => C:\ProgramData\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\keyiso.dll -> No File 
FolderExtensions_S-1-5-21-3046525360-976882445-4112316675-1000: [] -> {F6BF8414-962C-40FE-90F1-B80A7E72DB9A} => C:\ProgramData\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\keyiso.dll -> No File 
AlternateDataStreams: C:\ProgramData:iSpring Solutions [128] 
AlternateDataStreams: C:\ProgramData\Application Data:iSpring Solutions [128] 
AlternateDataStreams: C:\ProgramData\Reprise:wupeogjxldtlfudivq`qsp`27hfm [0] 
HKLM\...\RunOnce: [removeTempFiles936614] => cmd /c "del C:\Users\DAVIDS~1\AppData\Local\Temp\934055\uninstall.exe C:\Users\DAVIDS~1\AppData\Local\Temp\934055\smooth.dll C:\Users\DAVIDS~1\AppData\Local\Temp\934055\libgcc.dll C:\Users\DAVIDS~1\Ap (the data entry has 90 more characters). <==== ATTENTION 
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender: Restriction <==== ATTENTION 
HKU\S-1-5-21-3046525360-976882445-4112316675-1000\...\Winlogon: [Shell] C:\Windows\explorer.exe [3229696 2016-08-29] (Microsoft Windows -> Microsoft Corporation) <==== ATTENTION 
GroupPolicy: Restriction ? <==== ATTENTION 
Policies: C:\ProgramData\NTUSER.pol: Restriction <==== ATTENTION 
HKLM\SOFTWARE\Policies\Mozilla\Firefox: Restriction <==== ATTENTION 
C:\found.001
Task: {4961FD58-7DDB-482D-B588-89E01D3A178A} - \{2609CC50-DA76-4AFC-83C9-43A19C9B397F} -> No File <==== ATTENTION 
Task: {6F297FC2-1E71-42AD-B7BA-6BA247BEE2A8} - System32\Tasks\{258AC9D0-8C18-41CB-8142-FD1BC022128D} => C:\Windows\system32\pcalua.exe -a "C:\Users\davids home\AppData\Local\Temp\Temp1_CuteWriter.zip\converter.exe" <==== ATTENTION 
Task: {B6BC6465-0501-494D-B580-9CEEA7511655} - \movie -> No File <==== ATTENTION 
Task: {D9E0BFEB-AC33-4D5C-AE51-04345DDCC8BF} - \{B7FFB674-1F32-4651-8661-D3A4BDF8B84E} -> No File <==== ATTENTION 
HKU\S-1-5-21-3046525360-976882445-4112316675-1000\...\ChromeHTML: ->  <==== ATTENTION 
Task: {4961FD58-7DDB-482D-B588-89E01D3A178A} - \{2609CC50-DA76-4AFC-83C9-43A19C9B397F} -> No File <==== ATTENTION 
Task: {B6BC6465-0501-494D-B580-9CEEA7511655} - \movie -> No File <==== ATTENTION 
Task: {D9E0BFEB-AC33-4D5C-AE51-04345DDCC8BF} - \{B7FFB674-1F32-4651-8661-D3A4BDF8B84E} -> No File <==== ATTENTION 
FF Plugin-x32: @videolan.org/vlc,version=2.0.8 -> C:\Program Files (x86)\VideoLAN\VLC\npvlc.dll [No File] 
FF Plugin-x32: @videolan.org/vlc,version=2.1.2 -> C:\Program Files (x86)\VideoLAN\VLC\npvlc.dll [No File] 
FF Plugin-x32: @videolan.org/vlc,version=2.2.1 -> C:\Program Files (x86)\VideoLAN\VLC\npvlc.dll [No File] 
ShellIconOverlayIdentifiers: [00avg] -> {472083B0-C522-11CF-8763-00608CC02F24} =>  -> No File 
FolderExtensions: [] -> {F6BF8414-962C-40FE-90F1-B80A7E72DB9A} => C:\ProgramData\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\keyiso.dll -> No File 
FolderExtensions_S-1-5-21-3046525360-976882445-4112316675-1000: [] -> {F6BF8414-962C-40FE-90F1-B80A7E72DB9A} => C:\ProgramData\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\keyiso.dll -> No File 
HKLM\...\RunOnce: [removeTempFiles936614] => cmd /c "del C:\Users\DAVIDS~1\AppData\Local\Temp\934055\uninstall.exe C:\Users\DAVIDS~1\AppData\Local\Temp\934055\smooth.dll C:\Users\DAVIDS~1\AppData\Local\Temp\934055\libgcc.dll C:\Users\DAVIDS~1\Ap (the data entry has 90 more characters). <==== ATTENTION 
Task: {6F297FC2-1E71-42AD-B7BA-6BA247BEE2A8} - System32\Tasks\{258AC9D0-8C18-41CB-8142-FD1BC022128D} => C:\Windows\system32\pcalua.exe -a "C:\Users\davids home\AppData\Local\Temp\Temp1_CuteWriter.zip\converter.exe" <==== ATTENTION 
2021-01-22 14:51 - 2021-01-22 14:51 - 000000000 ____D C:\Users\davids home\AppData\Local\TempTaskUpdateDetection9C962C5B-8078-47EB-B527-545643EC8054 
CustomCLSID: HKU\S-1-5-21-3046525360-976882445-4112316675-1000_Classes\CLSID\{19A6E644-14E6-4A60-B8D7-DD20610A871D}\InprocServer32 -> C:\Users\davids home\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20244.4\x64\Microsoft.Teams.AddinLoader.dll (Microsoft Corporation -> Microsoft Corporation) 
CustomCLSID: HKU\S-1-5-21-3046525360-976882445-4112316675-1000_Classes\CLSID\{CB965DF1-B8EA-49C7-BDAD-5457FDC1BF92}\InprocServer32 -> C:\Users\davids home\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20244.4\x64\Microsoft.Teams.AddinLoader.dll (Microsoft Corporation -> Microsoft Corporation) 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:urLyIdmw66pmGCeXdl3Fz9SnrM [2642] 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:WKrGS1tLeTSnx6wwUHcWyvmQN [2166] 
HKLM\...\RunOnce: [removeTempFiles936614] => cmd /c "del C:\Users\DAVIDS~1\AppData\Local\Temp\934055\uninstall.exe C:\Users\DAVIDS~1\AppData\Local\Temp\934055\smooth.dll C:\Users\DAVIDS~1\AppData\Local\Temp\934055\libgcc.dll C:\Users\DAVIDS~1\Ap (the data entry has 90 more characters). <==== ATTENTION 
Task: {6F297FC2-1E71-42AD-B7BA-6BA247BEE2A8} - System32\Tasks\{258AC9D0-8C18-41CB-8142-FD1BC022128D} => C:\Windows\system32\pcalua.exe -a "C:\Users\davids home\AppData\Local\Temp\Temp1_CuteWriter.zip\converter.exe" <==== ATTENTION 
2021-01-22 14:51 - 2021-01-22 14:51 - 000000000 ____D C:\Users\davids home\AppData\Local\TempTaskUpdateDetection9C962C5B-8078-47EB-B527-545643EC8054 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:urLyIdmw66pmGCeXdl3Fz9SnrM [2642] 
AlternateDataStreams: C:\Users\davids home\AppData\Local\Temporary Internet Files:WKrGS1tLeTSnx6wwUHcWyvmQN [2166] 
U4 npcap_wifi; no ImagePath 
EMPTYTEMP: 
End::

• Right click on the highlighted text and select Copy.
• Start FRST (FRST64) with Administrator privileges
• Press the Fix button. FRST will process the lines copied above from the clipboard.

• When finished, a log file (Fixlog.txt) will pop up and saved in the same location the tool was ran from.

Please copy and paste its contents in your next reply.

 

Second:

 

Once done, enter your BIOS and change the boot order to the drive containing Windows 10 first, then the drive containing Windows 7 second. Save and Boot. Does Windows 10 boots as default?

 

If it does, run FRST64 in Windows 10. Make sure you tick List BCD and post its reports

[Advertisements]

Is being two days since our last conversation. Another 24 hours and I will close this topic.

[JSntgRvr]

Is being two days since our last conversation. Another 24 hours and I will close this topic.

[netrate]

Thanks for the reminder.  I am on it and will edit this post shortly with the update.

 

EDIT : the fixlog is attached.

 

I only have one drive whenever I run the computer.  I don't want to take a chance running both since I need them for work and can't afford another shutdown.

Edited by netrate, 01 February 2021 - 08:14 PM.

[iammykyl]

Gday.

Fix logs are not showing.   Were they for W10 drive?

[netrate]

I am only running this for Win 7 right now.  Is that ok to complete one drive at a time?  As I said, I am disconnecting each drive, depending on which I am using.

Attached Files

•  Fixlog.txt   16KB   124 downloads

Edited by netrate, 01 February 2021 - 08:26 PM.

[iammykyl]

There may be a little confusion, so to clarify.

Do not run the fixit on the W10 drive, that was from post #121; that fix was for the W7 Drive.

Also, do not change the boot order in the BIOS.

 

'I will be back in half an hour.

[netrate]

Ok, so we are clear then.

I have only run from Win 7.  I don't change the boot order, I always start the boot using f12 and select the Win 7 drive.  If you want me to set the boot order in the bios, I will. I must have missed that somewhere.  The bios will always be a bit screwy because I am constantly changing the drive if I have to use Win 10 or Win 7.  Therefore, those drives are being taken from the bios boot each time and pushed farther down the list (I also have my 1TB storage drive that is non-boot and always connected).  Let me know if that makes sense.

[iammykyl]

Yes all is clear.

We have to wait for JSntgRvr  to come back and look at the fixit  log result.

Then, I think, you will have to run FRST64 on the W10 disk to see what state it is in.   So you will need to download it and install to the W10 disk.

 

REMINDER for when you need it. 

Please download https://www.techspot...-scan-tool.html and save it to your Desktop.
Note: You need to run the version compatible with your system. If you are not sure which version applies to your system download both of them and try to run them. Only one of them will run on your system, that will be the right version.

• Right click to run as administrator (XP users click run after receipt of Windows Security Warning - Open File). When the tool opens click Yes to disclaimer.
• Press Scan button.
• It will produce a log called FRST.txt in the same directory the tool is run from.
• Please copy and paste log back here.
• The first time the tool is run it generates another log (Addition.txt - also located in the same directory as FRST.exe/FRST64.exe). Please also paste that along with the FRST.txt into your reply.

[netrate]

Ok, it is close to 11pm here, I am going to have to try running FRST on the WIN 10 tomorrow.

NOTE :  Although I have lived in Australia in my youth, my body can no longer keep up with the 20+ hour time difference.

[iammykyl]

OK. when you come back.

Did you image both drives?

[JSntgRvr]

Ok, so we are clear then.

I have only run from Win 7.  I don't change the boot order, I always start the boot using f12 and select the Win 7 drive.  If you want me to set the boot order in the bios, I will. I must have missed that somewhere.  The bios will always be a bit screwy because I am constantly changing the drive if I have to use Win 10 or Win 7.  Therefore, those drives are being taken from the bios boot each time and pushed farther down the list (I also have my 1TB storage drive that is non-boot and always connected).  Let me know if that makes sense.

 

I need you to change the boot order and select the Windows 10 drive to boot first and the Windows 7 drive to boot second. I dont want you to use F12 to select the drive. Once the boot order is set, have both drives connected and boot. It should boot to Windows 10 by default. Then, and only then Run FRST64 in Windows 10, put a tick on List BCD and Addition.txt and Scan. Post the resulting reports.

[netrate]

Ok, I know I am asking for help, but I am very wary of hooking up both drives again.  If I lose my win 7, I cannot work.  Win 10 I can deal with.  I was hoping to try and solve this one drive at a time before hooking them both up again.  

[iammykyl]

Ok, I know I am asking for help, but I am very wary of hooking up both drives again.  If I lose my win 7, I cannot work.  Win 10 I can deal with.  I was hoping to try and solve this one drive at a time before hooking them both up again.  

I understand you being wary.   We have to wait for JSntgRvr  to come back before proceeding meanwhile, please answer.

You ran a fixit for the W7 disk, from post $121.

1.   Does W7 boot normally now, without first running a chkdsk?

2.   Does W10 ruin normally.

3.   Have you taken an image of the W7 disk and checked you can access it?

[JSntgRvr]

Ok, I know I am asking for help, but I am very wary of hooking up both drives again.  If I lose my win 7, I cannot work.  Win 10 I can deal with.  I was hoping to try and solve this one drive at a time before hooking them both up again.  

In order to perform a dual boot, both drives must be connected to the board. The BIOS must detect the presence of both drives. The boot order in the BIOS, also depends on these connections. You must either clone the drive or backup all your data. To proceed, you must connect both drives to the board.

[netrate]

Iammmky,

 

After running the fix, it still dskchcks when booting win 7 (running solo + storage drive)

-Win 10 runs but still dskchcks the drives (running solo + storage drive)

 

I have created an image of both win 7 and win 10 in the last two weeks.

Again, I am still very wary of this at present because even with a disk image using MR (and you can call me paranoid), I am worried I would not be able to get this running for work.  My rational has to do with "creating restore" points which should be full-proof and yet, in my recent experience, not being able to find said restore points when my system crashed from the advanced options and the MCT.  This happened on both Win 7 and Win 10.  Restore points not found even though I made successful restore points the night before.

 

That is probably why I have been putting this off.  At present, I can't be sans-computer if something goes awry.