Windows 10: did Microsoft enhance NTFS in anniversary update?

did Microsoft update or enhance the NTFS file system in the
anniversary update cause i am having severe permission issues
cause my puter cant duel boot i boot from a removable HDD's
my HDD began to run out of space so i got a 6TB hdd and put w8
on it then upgraded to win 10 pro both HDD's use the same computer
hardware cpu and mobo and same activation code and same microsoft account
now some of my hdds i use for storage cant be accessed when i switch the boot hdd
the same goes for ne folders created and files coppied...one hdd i rename and when
i switch boot hdds the name on the drive is the same before i renamed it...needles to say i am a bit angry and this just recently started happening...any help appreciated tnx Gene

:)

 

Windows 10 updated [all my external hard disk] is not accessible. the request is not supported

To all concerned !!!!

The Windows Anniversary Edition does not read HDDs or Pen drives or any form of removable storage that has been formatted in NTFS with a GPT partition .. Specially if you have added or deleted a partition or even resized one.

The solution would be :

1. Backup your Drive on an other computer with a Non Windows Anniversary Edition.

2. After Backup Re Format Your HDD on the same machine to NTFS or Fat 32 whichever you require.

3. Move the data back to the HDD ...

It should read correctly and probably better

Hope this solves your problem....

 

Kernel power 41 shot down

The table below shows the connection between Events 41 and 98.

Error 23/02/2017 06:44:14 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 22/02/2017 18:15:10
Kernel-Power 41 (63)

Error 22/02/2017 18:15:10
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 22/02/2017 17:52:45 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 22/02/2017 12:57:54 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 22/02/2017 12:44:17
Kernel-Power 41 (63)

Error 22/02/2017 12:44:17
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 22/02/2017 12:36:13 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 18/02/2017 09:12:57
Kernel-Power 41 (63)

Error 18/02/2017 09:12:57
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 18/02/2017 08:21:23 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 16/02/2017 09:15:13 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 16/02/2017 07:36:52 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 15/02/2017 19:56:24 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 15/02/2017 18:09:03
Kernel-Power 41 (63)

Error 15/02/2017 18:09:03
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 15/02/2017 14:00:38 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 14/02/2017 18:46:25 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 13/02/2017 10:19:45
Kernel-Power 41 (63)

Error 13/02/2017 10:19:45
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 13/02/2017 08:15:15 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 12/02/2017 18:04:41 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 12/02/2017 14:43:06 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 12/02/2017 14:16:25
Kernel-Power 41 (63)

Error 12/02/2017 14:16:25
Ntfs (Microsoft-Windows-Ntfs) 98
None

Critical 12/02/2017 13:54:24
Kernel-Power 41 (63)

Error 12/02/2017 13:54:24
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 12/02/2017 12:31:50 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 11/02/2017 14:35:21 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 11/02/2017 14:34:57 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 11/02/2017 10:34:45 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 10/02/2017 19:54:58
Kernel-Power 41 (63)

Error 10/02/2017 19:54:58
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 10/02/2017 14:30:49 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 10/02/2017 13:53:24
Kernel-Power 41 (63)

Error 10/02/2017 13:53:24
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 10/02/2017 13:45:00 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 09/02/2017 18:56:18
Kernel-Power 41 (63)

Error 09/02/2017 18:56:18
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 09/02/2017 18:51:13 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 09/02/2017 13:56:00
Kernel-Power 41 (63)

Error 09/02/2017 13:56:00
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 09/02/2017 11:46:31 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 09/02/2017 10:34:43
Kernel-Power 41 (63)

Error 09/02/2017 10:34:43
Ntfs (Microsoft-Windows-Ntfs) 98
None

Critical 09/02/2017 10:02:06
Kernel-Power 41 (63)

Error 09/02/2017 10:02:06
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 09/02/2017 06:29:50 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 08/02/2017 19:14:23 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 08/02/2017 16:52:18 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 07/02/2017 20:23:46
Kernel-Power 41 (63)

Error 07/02/2017 20:23:46
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 07/02/2017 19:02:39 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 07/02/2017 19:02:12 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 07/02/2017 17:47:55 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 07/02/2017 16:52:45 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 02/02/2017 18:57:10 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 02/02/2017 12:34:15
Kernel-Power 41 (63)

Error 02/02/2017 12:34:15
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 02/02/2017 07:50:43 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 01/02/2017 19:56:30
Kernel-Power 41 (63)

Error 01/02/2017 19:56:30
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 01/02/2017 18:24:33 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 01/02/2017 12:41:09 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 31/01/2017 14:35:39 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 30/01/2017 13:14:06 Ntfs (Microsoft-Windows-Ntfs)
98 None

Critical 30/01/2017 13:08:28
Kernel-Power 41 (63)

Error 30/01/2017 13:08:28
Ntfs (Microsoft-Windows-Ntfs) 98
None

Critical 30/01/2017 12:59:43
Kernel-Power 41 (63)

Error 30/01/2017 12:59:43
Ntfs (Microsoft-Windows-Ntfs) 98
None

Error 30/01/2017 12:37:02 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 29/01/2017 12:55:17 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 28/01/2017 20:24:38 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 28/01/2017 13:32:48 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 28/01/2017 10:06:41 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 27/01/2017 19:56:09 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 27/01/2017 12:50:22 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 27/01/2017 08:53:23 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 26/01/2017 18:53:59 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 26/01/2017 08:18:48 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 25/01/2017 18:13:25 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 25/01/2017 14:37:43 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 25/01/2017 10:51:51 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 25/01/2017 08:08:40 Ntfs (Microsoft-Windows-Ntfs)
98 None

Error 24/01/2017 08:51:02 Ntfs (Microsoft-Windows-Ntfs)
98 None

 

Just musing. How old is the computer? I have 2 just old enough that I can't use over 2TB drives, BIOS problems.

 

the mobo is about 3 or 4 years old and I built it my self
mobo is a 990FX Extreme9, cpu fx8350 4ghz, 32GB ddr3 mem.
and yes I replaced the battery and re setup the bios

 

Please learn how to use capital letters and full stops!!!

 

Please learn not to use multiple exclamation marks as it is not grammatically correct!

 

Nope, it hasn't changed since version 3.1 released with Windows XP in autumn 2001 (NTFS - Wikipedia)

The problem sounds like it is due to the way permissions work in NTFS. The access to a file is based on your Security Identifier (or SID) which is a unique random looking number and not the same as your user name.

From your description I guess you have 2 different SIDs and so you aren't authorized. What you need to do is right click on the drive(s) you aren't authorized to, go to Properties > Security > Edit and add your user (and probably the administrators group as well).

See option 2 here :Permissions - Allow or Deny Access to Users and Groups in Windows 8

You may need to take ownership first in which case see option 4 here Owner of Files and Folders - Change in Windows 10 - Windows 10 Forums

 

AFAIK this is not entirely accurate, as people dual booting XP and later Windows versions may discover. However, the usual complaint is an issue with backward compatability, which causes XP to run a disk check when it sees a partition that 10 has written to previously. This is not the situation posed by the OP, which you rightly point out is probably a permissions issue.

Even within NTFS 3.1 there are changes that have minor impact on compataiblity.

This behavior has been reported on several occasions it is, although undesirable, "by design", because WinXP and Win7 use slightly different structures in their filesystems, and WinXP interprets the Win7 filesystem as "having errors", and the opposite will also occur -- Win7 will see "errors" on the WinXP filesystem.


https://social.technet.microsoft.com...w7itproinstall

 

That's interesting. Certainly on my 1607 install fsutil fsinfo ntfsinfo C: still shows NTFS version 3,1 (same as XP).

I guess I shouldn't believe everything on Wikipedia *Smile

 

The only reason I came across this is that I was bitten by this phenomenon and went looking for a reason.

I was playing with Win8 ToGo on a machine whose installed OS was XP.
On the next XP boot, it always ran chkdsk. This did not seem to be a NTFS "dirty bit" issue, so I dug a little deeper.
Unlike, say, a live Linux disk which totally ignores the contents of the internal hard drive unless you explicitly mount it, busybody Windows simply can't leave well enough alone. It insists on doing things by default (like running Windows Defender on every attached drive).

 

I have tried adding me and admin and taking ownership this
problem just recently started. I upgraded from w8 pro not xp,
I am not actually dual booting, I am using a removable HDD tray
I am swapping HDD's with the tray but both have windows 10 pro on
them with the same activation code and the same Microsoft account,
is there anyway to synchronize the Sid . besides if I delete the partition
and create a new partition the drive should not show up when I swap the boot drive
with the old drive name and files and folders on it and it does but some files and
folders cant be accessed and some can. . this has got me baffled...

 

Don't think it's possible to synchronize different SID's after the fact.

I don't know whether this is endorsed - it certainly isn't the safest method, but what has worked for me is this:

If I'm using an external NTFS-formatted drive that I intend to swap between several computers, I prepare the drive ahead of time by giving root ownership and access to "Everyone".

Also, something like this may be of use:

JSWare - Utilities For Fixing NT6

 

Definitely not. It would be completely absurd if you could do that. You may as well not have any security at all.

Me too. For example the drive I download torrents to is set to allow everyone RW access as it just makes it easier for me. (my Transmission Client runs on Arch Linux)

It needn't be the whole drive though - it can be a share or directory - however you deal with your security.