Windows 10: Odd ChkDsk error on Win10 64 bit that I have never seen and cannot find adequate info about.

Hello,

When running ChkDsk /f or /r, we are repeatedly seeing the error:

----
Stage 1: Examining basic file system structure ...
The allocated length 0xaeb000 is not in multiple of 0x10000 for attribute of type 0x80 and instance tag 0x0.
----

But then at end of ChkDsk report:

----
Windows has scanned the file system and found no problems.
No further action is required.
----

Additional comments:

1) We get identical results running ChkDsk repeatedly.

2) This error message does not even appear when running ChkDsk without /f or /r, which we find odd since we thought errors should be reported regardless, even though not fixed.

3) Including /v is of no help because no additional information is added to the report (we are on NTFS, not FAT32).

4) We have been running the system for several weeks without obvious problem, but are nervous as the system is going into a 12x7x365 museum environment.

5) We ran SFC /scannow and it detected no errors.

6) We made a copy of the drive and tried to run ChkDsk/f from a Win7 64 bit machine just to see if that would fix the issue, but apparently Win10 and Win7 file structure sufficiently different that that is not possible. (Message in question did not appear, but dozens of other issues not present with Win10 ChkDsk did.)

7) Looked online extensively for info based on message text, but no luck.

8) Ran complete hardware scan of disk using drive manufacture utility - no problems. (And made copies of this drive to others, with identical error, so seems relatively certain that, it this point anyway, it is a software file structure issue, unrelated to disk hardware failure.)


Thoughts, comments, advice? Like:

a) (The probably impossible question of) How nervous should this make us?

b) Might this be a bug in ChkDsk? Not necessarily that we don't indeed have a problem, but that ChkDsk is not fixing it, saying that all OK, etc.?

c) Any quick way to track down offending file? (If a file is even the issue.)
(We are in process of trying to do by manual binary search, dividing OS partition in half and running ChkDsk /f on it, but that is very tedious...)

Thanks,
David

:)

 

Dual Boot Win10 64 bit and Win10 32 bit

When I originally installed Win10 I installed the 32 bit version. I have a blank drive, and would like to install the 64 bit version on that, creating a dual boot system.

What are the steps I need to follow? I'm reasonably intelligent but not tech savvy.

 

Win10 32 bit migration to 64 bit

I have an HP 6200 Pro running perfectly with a fully updated and activated license for Win10 Pro 32 bit. I am contemplating a migration to 64 bit Win10 Pro and have downloaded a 64 bit ISO file on a USB drive which is bootable right now. A 9/15/2015
Post on "Groovypost.com" says that on a UEFI based PC (as mine is), the USB drive must be made bootable with a utility such as "Rufus" making sure to format it in FAT32 and using the GPT Partitioning scheme. If the USB drive is already bootable, why would
this be suggested?

Just how it is for UEFI..

Also, MS' directions says that a product key will NOT be required if upgrading (in my case migrating) from an activated copy of Win10. Is this correct and if so, where does the new SW pick up the old activation digital entitlement - from the in place
activated copy of Win10 32 bit?

The computer configuration is known to Microsoft, and when 64-bit is installed, it takes note and activates automatically. All you have to do is skip the part where you are asked to enter a key code..

 

Win10 32 bit migration to 64 bit

I have an HP 6200 Pro running perfectly with a fully updated and activated license for Win10 Pro 32 bit. I am contemplating a migration to 64 bit Win10 Pro and have downloaded a 64 bit ISO file on a USB drive which is bootable right now. A 9/15/2015 Post
on "Groovypost.com" says that on a UEFI based PC (as mine is), the USB drive must be made bootable with a utility such as "Rufus" making sure to format it in FAT32 and using the GPT Partitioning scheme. If the USB drive is already bootable, why would this
be suggested? Have the updates in the last 5 months made this possible?

Also, MS' directions says that a product key will NOT be required if upgrading (in my case migrating) from an activated copy of Win10. Is this correct and if so, where does the new SW pick up the old activation digital entitlement - from the in place activated
copy of Win10 32 bit?

Thanks for your time, the MS Community is extremely helpful.

Bob Munoz