Acl problem on ssd drive (Win 10)

[Herrie]

Hello forum,

I am having an "ACL" problem on my (former) windows 10 drive.
Windows does not start up, I simply get no access to any folder/directory.
So I temporarily istalled Windows on another drive, hoping to get things right while the originl drive is connected to my system. I bought and used Windows Repair Pro, but it just repairs the windows drive on which it is installed.
Is there a way to make/force Windows Repair to handle the other drive?

To 'visualize' my situation:

Drive 1
- c:/windows

Drive 2 (named "Z")
- z:/windows

WIndows repair utilities all refer to "c"

Where to change tis in an existing script? So I can make it work on "Z".
Of course the changed script is to be saved under another name, e.g. '_z_ [old name]

Looking forward to replies and options

Harry

[Boggin]

The repair program only works from within Windows so will only work on the drive that is booted up.

With just the affected drive installed, there are a couple of methods to get into the diagnostic mode which are where you boot up with the install media and select Repair your computer on the Install screen - Troubleshoot - Startup Repair or switch on then power shutdown when you see the Windows logo then do that another twice where the diagnostic mode will start for you to navigate to the same advanced options.

Using the latter method, if the Startup Repair reports that it is unable to auto repair your computer then click on Advanced options and select Command Prompt and enter chkdsk c: /f to see if that will repair the file structure.

That is more difficult if you've booted up with install media as it doesn't always see the volume as being in C:

Normally entering the cmd bcdedit |find "osdevice" will give you the partition letter to use in the chkdsk cmd, but if it doesn't see the volume then it would be a guess as to which letter to use.

Mine can come up as D: or E:

For clarity, that is a Pipe symbol before find and is the uppercase of \

You can also check the status of the SSD with both drives installed by using the trial version of HDSentinel.

Download the Trial v5.30 (ZIP) version - https://www.hdsentinel.com/download.php

Uninstall when done which will stop the clock on the 30 day trial and then you can use it again as and when by reinstalling it from your Downloads folder.

[Herrie]

I will try to descibe my problem better.
Situation:
- windows 10 pro installed (minimal) on a sperate device. (Call this A)
- windows 10 (with all my programs) still on another (SSD) drive (Call this B)

When A is booted and running, I managed to see all files and folders of B in Win Explorer and can copy, mobe, etc those using elevated cmd.
I renamed this Partition Z:

I managed to install the Tweaking.com on B

Tweaking, on B, even starts from commandline or 'run' in explorer.

However, it acts on A, which is the 'active' Windows 10 installation.

Knowing that all files on B are still present and in tact, I think it could run on B (being my Z: partition).

My Question is......
Is it possible to change all references from C: to Z:?
If so, where have these changes to be made?

Example: %SYSTEM%  > > Z:\SYSTEM%\

Perhaps this 'drive' or partition reference could be part of the tweaking application.

Looking forward to a reply

[Boggin]

To run the repair program on B, B would need to be the booted drive.

Will B boot with A disconnected ?

I'll ask my support to have a look at your set up.

[Herrie]

B does not boot when attached as single drive.
I susspect a problem in the boot file

[Boggin]

If you have an UEFI BIOS you may have to turn off Secure Boot.

You can get into the BIOS by pressing and holding F2 as you switch on.

[Herrie]

Securenbootnis not an available option in my bios.
Option Uefi is on.

Booting ends with
No system disk or disk error
No bootable device found

Diskpart shows 3 partitions on the drive

One small  about 100 Mb
One 500 Mb (recover)
The large windows partition.

An effort to run the Tweaking repair in Dos, after booting on recovery USB does not work
It can not run under this dos version.

[Boggin]

Can you follow the steps in the second paragraph of my first post to see if you can get into diagnostic mode.

[Herrie]

Bcdedit results in partition c,which is the actual partition I am running

[Herrie]

Possible solution!

As I can copy/move etc, I can make a partition backup with aomei to another drive, not being A or B.

Is it a solution to reinstall windows 10 om B, and restore the backup I made before?

[Boggin]

Did you boot up with install media or shutdown and restart 3 times ?

Doing the latter will invoke the diagnostic mode.

Just seen your last post.

If you reinstall Win 10, the backup you made previously would have the problems it has now if that was a system image.

The fact that it can see the volume as being in C: would suggest the startup is corrupt which the diagnostics can sometimes fix.

Try shutting down and restarting as I've described and see what diagnostics can do with the B drive.

If that reports it is unable to auto fix, then select Advanced options and select Command Prompt and enter chkdsk c: /f which will also report if there are any KBs in bad sectors on the drive as well as repairing the file structure.

If it does report bad sectors then redo the chkdsk as chkdsk c: /r then make your system image ASAP as the drive will eventually fail.

[Herrie]

My idea was to use the recovery Win10 install, meaning, losing all my personal files and programs.
Next to restore the backup of the  windows partition on B.
That means including the $#### files (system files, aren't they?)

I thought that this would repair the boot action, startup the restored Win10 backup.

Is it true that this will cause troubles again? If so, which are to be expected? Are those repairable?
I guessed that the restored copy incluses all register settings

[Boggin]

Your system image will be of what you have now, so you would just be putting that back on.

There is a Reset option that retains your personal stuff but removes any installed programs, but the diagnostics mode of Win 10 can repair start up problems.

I'd give that a try first and you need to check the status of the drive as to any bad sectors.