[netrate]

I think I am going to have to start a new thread on this one.

 

Win 10 (samsung SSD 500) /win 7 (Kingston 120gig SSD) dual boot.

Gigabtyte - GA-970A-D3 v 1.4

 

Up until yesterday win 10/win 7 were managing to work.

  

0) I have been creating restore point weekly on each system

1) Win 10 stopped booting and got the BlackSOD

2) Safe mode did not work

3) Start up repair did not work for advanced 

4) Start up repair did not work for Media Creation tool

5) I made a restore point in win 10 the night before the BSOD - when trying to use the restore point it said "No restore points founds"

 

So this was my next step - 

In win 7, I wanted to copy what I needed from Win 10 and possibly start over with win 10.  BUT in win 7, it does not let me access my win 10 drive anymore, not as a slave drive -- but it used to, very easily.

 

I can see the win 10 drive from win 7 (and all the partitions), but it tells me ACCESS is DENIED to only the main window drive (the one with all my windows files on it).

I don't know how this has suddenly happened.

 

A further question - if I have a drive with partition and I have saved a restore point in win 10 on them, it is possible it has saved the restore point somewhere else?  If so, how can I access restore points from other locations or even find them?

 

Lastly I have tried from win 7 to get permissions through explorer and when it reaches RECOVERYtxt, it says

"An error occurred while applying security information to e: recovery.txt,  access is denied"

 

EDIT : I can see the drive fully in the cmd prompt.

I am in the process of trying to copy the files I need via cmd prompt to backup drive. Why I cannot do this in Win 7 file explorer, I don't know!

 

Here is what my Win 10 drive looks like from Win 7 

I can access Drive F and H, but not E - that funny icon is from me trying to gain permissions to the drive.

Attached Thumbnails

• 

Edited by netrate, 21 January 2021 - 01:24 PM.

[Advertisements]

netrate.

 

 

Your malware thread has been reopened so this thread will be closed.

[phillpower2]

netrate.

 

 

Your malware thread has been reopened so this thread will be closed.

[JSntgRvr]

User wish to continue his non malware post. I am therefore opening this topic.

[netrate]

I am now able to boot both drives, but only separately.  Win 10 was fixed with Custom Install..

Having issues now with chkdsk each time each separate drive boots.

[iammykyl]

I am now able to boot both drives, but only separately.  Win 10 was fixed with Custom Install..

Having issues now with chkdsk each time each separate drive boots.

Your drives are,

a) Win 7 - Kingston 120gig  SSD -(chkdsk runs at every Boot) this is your work drive.

b) Win 10 - Samsung 500gig SSD (chkdsk runs at every Boot) fixed with a custom install.

c) 240gig Kingston SSD (W10 install, present condition not determined)

d)1TB WD Storage drive (non-boot, this drive is always connected.)

Motherboard : gigabyte GA-970A-d3 version 1.4

===================================================================

We will try to get W10 on the Samsung 500gig to work before anything else. 

 

​What do you mean by a "custom install"?

Did you install from a MCT, them, new install of drivers and programs, them, copy over user Data? or another method?

[netrate]

When I lost win 10 (again) and advance startup or MCT startup repair did not fix it.  So I used the custom install following these instructions which gave me a windows.old file. 

 

https://www.tenforum...ndows-10-a.html

[iammykyl]

OK.

Trying to stop chkdsk running, 

Connect W10 drive to SATA port #0

Connect 1TB storage to SATA Port #3

Connect DCROM to SATA Port #5.

===================================

Start the computer and enter the BIOS.

In the right window, select > Load Optimized Defaults > Save >exit.

When Windows starts, allow chkdsk to run, when finished exit the window.

===============================

In W10, run CMD as Administrator.

Copy and paste the following, (replacing g at each prompt with the correct drive letter.)

 

fsutil dirty query G:

This command will query the drive, and more than likely it will tell you that it is dirty.

Next, execute the following command:

 

CHKNTFS /X G:

The X tells Windows to NOT check that particular drive (G) on the next reboot.

 

At this time, manually reboot your computer, it should not run Chkdsk now, but take you directly to Windows.

Once Windows has fully loaded, bring up another command prompt and execute the following command:

Chkdsk /f /r g:

This should take you through five stages of the scan and will unset that dirty bit. Finally, type the following and hit Enter:

fsutil dirty query g:

Windows will confirm that the dirty bit is not set on that drive.

Exit CMD > Restart.

 

 

Results please. 

 

 

, 

[netrate]

I am going to work through this a bit at a time.  I will get out the manual for the MOBO, It is a pretty tight squeeze to try and set the SATA locations correctly.

The Win 10 drive is 500gig, just wondering how long the Chkdsk is going to take for something like that?  The reason being is that I will be without a computer for a while -- should I run that overnight?

Also in the BIOS will loading the OPT defaults change anything major?  Remember, I still need to get back to Win 7 for work (which I am presently doing now).

 

OK.

Trying to stop chkdsk running, 

Connect W10 drive to SATA port #0

Connect 1TB storage to SATA Port #3

Connect DCROM to SATA Port #5.

===================================

Start the computer and enter the BIOS.

In the right window, select > Load Optimized Defaults > Save >exit.

When Windows starts, allow chkdsk to run, when finished exit the window.

 

[iammykyl]

 should I run that overnight?

Also in the BIOS will loading the OPT defaults change anything major?  Remember, I still need to get back to Win 7 for work (which I am presently doing now).

 

 

 

Really hard to say how long chkdsk would run, from Google searching, I estimate 3 hours; try to start as soon as you finish work, it must run to 100%, 

If you run out of time for the whole process, you can, after the CHKNTFS /X G: and a restart,

leave these steps to the following night

> Chkdsk /f /r g:

This should take you through five stages of the scan and will unset that dirty bit. Finally, type the following and hit Enter:

fsutil dirty query g:

Windows will confirm that the dirty bit is not set on that drive.

Exit CMD > Restart.

 

Changing to OPT Defaults will not effect the actual boot process, just makes sure there is no overclock settings or any other altered setting that are not normal, accidentally or user set. 

[netrate]

Trying this tonight and will report back.  It's been a busy week, month, year.

[iammykyl]

[iammykyl]

Gday netrate.

How are you progressing with the chkdsk issue?

[netrate]

Well, I ran the win10 scan disk.  Left it overnight.  

Ran the fsutil dirty query G: and this came up :

 

Not dirty (see attached)

 

I was not sure how to proceed at this point since it says not dirty.

 

 

 

Attached Thumbnails

• 

[iammykyl]

Looks like you had all drives connected? for the moment, just work on the W10 drive.

Run the next command then restart the computer.

 

In W10, run CMD as Administrator.

Copy and paste the following, (replacing g at each prompt with the correct drive letter.)

> CHKNTFS /X G: > restart, chkdsk should not run.

-----------------------------------------

 

Next step is to ensure that System Restore is working.

Please read, I would use Option 1. > https://www.tenforum...ndows-10-a.html

 

There are also some useful links at the bottom of the aricle. 

[netrate]

It booted, no issues.  Did not do the disk check this time.

 

Yes, there are two drives

Win 10 - Samsung SSD 500gig

Storage drive - 1 TB platter drive

 

I don't really use the DVD rom anymore and that can be eliminated (I actually forgot about it) I have an external usb DVD  I can use.

 

Here is the result of the NTSF check:

Note : I am going to have to switch things around today since I do need to work with Win 7 this morning (disconnect the win 10 drive and connect the win 7 instead), but I will come back to win 10 after I see your post.

Attached Thumbnails

• 

Edited by netrate, 28 February 2021 - 09:37 AM.