3 Likes
3 Likes
meh, a girl became a millionaire for pretending to be a dog 
6 Likes
Nothing.
Prompted by the kind of (laughable) language both the tweet and the article were written in, I’ve tested this on a VM (win10 build 19041.746) hosted by an ESX with HDD storage array, and then on a laptop (win10 build 19041.450) with an SSD.
I wasn’t expecting much to happen, but… I got less than that.
What actually happens:
Being unable to access the indicated path, Windows assumes it encountered a corrupted file record in the MTF. (cause of apparently botched exception handler for this case)
A corruption was discovered in the file system structure on volume C:.
The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x5000000000005. The name of the file is “”.
This does not mean...
…a “corrupt NTFS-formatted hard drive”, “hard drive errors”, “corrupt the filesystem index”, “corrupts the drive” or any of the horseshit this tabloid claims it means and happens.
When it comes to the results of this “attack”, the screen shot from the tweet is the only true bit in this “story”.
The dirty bit is set for the volume accordingly, and that’s why chkdsk runs on reboot. You can check it (with fsutil dirty query c:) before and after you execute the “attack”.
chkdsk logs gathered after the reboot show no signs of bad file records. Nothing got corrupted, so there was nothing to repair:
chkdsk log from win10 build 19041.450 - laptop, SSD
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Stage 1: Examining basic file system structure …
660224 file records processed.
File verification completed.
Phase duration (File record verification): 4.18 seconds.
10948 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 6.74 milliseconds.
Stage 2: Examining file name linkage …
1029 reparse records processed.
908148 index entries processed.
Index verification completed.
Phase duration (Index verification): 19.03 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.26 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.32 seconds.
1029 reparse records processed.
Phase duration (Reparse point and Object ID verification): 19.89 milliseconds.
Stage 3: Examining security descriptors …
Cleaning up 9653 unused index entries from index $SII of file 0x9.
Cleaning up 9653 unused index entries from index $SDH of file 0x9.
Cleaning up 9653 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
Phase duration (Security descriptor verification): 219.29 milliseconds.
123963 data files processed.
Phase duration (Data attribute verification): 7.60 milliseconds.
CHKDSK is verifying Usn Journal…
41780672 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 119.43 milliseconds.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
No further action is required.
484375551 KB total disk space.
417242524 KB in 424333 files.
281752 KB in 123966 indexes.
0 KB in bad sectors.
786099 KB in use by the system.
65536 KB occupied by the log file.
66065176 KB available on disk.
4096 bytes in each allocation unit.
121093887 total allocation units on disk.
16516294 allocation units available on disk.
Total duration: 27.22 seconds (27224 ms).
Internal Info:
00 13 0a 00 d4 5d 08 00 1d d5 0e 00 00 00 00 00 …]…
46 03 00 00 bf 00 00 00 00 00 00 00 00 00 00 00 F…
Windows has finished checking your disk.
Please wait while your computer restarts.
chkdsk log from win10 build 19041.746 - VM, ESX, HDD array
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure …
96256 file records processed.
File verification completed.
Phase duration (File record verification): 12.87 seconds.
1762 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 2.06 milliseconds.
Stage 2: Examining file name linkage …
74 reparse records processed.
145730 index entries processed.
Index verification completed.
Phase duration (Index verification): 1.66 minutes.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 127.08 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.08 seconds.
74 reparse records processed.
Phase duration (Reparse point and Object ID verification): 6.64 milliseconds.
Stage 3: Examining security descriptors …
Cleaning up 98 unused index entries from index $SII of file 0x9.
Cleaning up 98 unused index entries from index $SDH of file 0x9.
Cleaning up 98 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 1.16 seconds.
24738 data files processed.
Phase duration (Data attribute verification): 2.57 milliseconds.
CHKDSK is verifying Usn Journal…
17822728 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 3.43 seconds.
Stage 4: Looking for bad clusters in user file data …
96240 files processed.
File data verification completed.
Phase duration (User file recovery): 25.12 minutes.
Stage 5: Looking for bad, free clusters …
4820651 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
32982342 KB total disk space.
13478320 KB in 69620 files.
58756 KB in 24739 indexes.
0 KB in bad sectors.
162658 KB in use by the system.
45472 KB occupied by the log file.
19282608 KB available on disk.
4096 bytes in each allocation unit.
8245585 total allocation units on disk.
4820652 allocation units available on disk.
Total duration: 27.17 minutes (1630351 ms).
Internal Info:
00 78 01 00 a2 70 01 00 0d 05 03 00 00 00 00 00 .x…p…
15 00 00 00 35 00 00 00 00 00 00 00 00 00 00 00 …5…
Windows has finished checking your disk.
Please wait while your computer restarts.
To sum up: it’s an annoying* bug, can be exploited for a practical joke, but it doesn’t pose any threat.
*because the only way to clear the dirty bit manually is with a hex editor; otherwise you need to let the chkdsk run a scan to clear it.
6 Likes
how does that compare with their on poc, their sources, and then the replies in their comments getting their own results too tho?
why such weird discrepancy - and why sound “alarm” like that if it’s actually nothing? - because that just makes the article and everything in it even weirder @_@
4 Likes
What discrepancy? No proof of results of this “attack” was provided, neither by them, nor the source.
(I’m not addressing the delivery of it, that part is obviously true regardless of whether we’re talking about this exploit or not.)
I’ve looked through the comments now (for the article and the tweet). People who bothered testing it are getting the same results I did.
The facts end where the journalism begins. It pays the bills for some people.
6 Likes
3 Likes
6 Likes
The act states that a president cannot destroy records until he seeks the advice of the national archivist and notifies Congress. But the law does not require him to heed the archivist’s advice. It does not prevent the president from going ahead and destroying records
meaningless laws are so awesome 
6 Likes
And to think, here in America we have millions of men who do nothing for FREE.
When they’re not rioting at the US Capitol or pretending to be President or Vice President.
4 Likes
Like this:
So much winning in this picture I can barely even stand to look at it. I have a subscription to the magazine and the articles about this disaster of an administration have never been kind. Yet he never mentions them. I don’t know why.
Another thing I’ve never heard him mention is this:
Joe Biden’s Island on Animal Crossing
I don’t understand why. He wigs out when anyone is getting 1 iota of attention he isn’t getting. Now I don’t follow the Orange Troll, I only know when he exploded if it was trending on Twitter or in the WaPo or someone told me, but just from what I’ve read about him, I know this would have set him off.
Did they make the decision NOT to tell him about this? It’s the only thing that makes sense to me.
5 Likes
I’m not entirely sure “rioting” is the most accurate term.
3 Likes
I always try to err on the side of caution and non inflammatory rhetoric on a public board.
Ila
4 Likes
what term would you use then? 
2 Likes
Major media outlets are using riot, so I guess that would be the most proper term.
2 Likes
major media outlets also used this term once
not so sure we should let “what to label it” be up to them
idono, in my opinion, despite what media or politicians may/would call it, when people behave that way, it’s rioting, regardless of what they protest for or against, so to me the capitol “incident” was clearly no doubt a riot
5 Likes
OK fine, I was just trying to blow it off.
By major media outlets, I mean I looked at what Reuters was saying plus what I remembered seeing.
When I first read rioting I was thinking there was another level of intensity. So like how rioting is a level of intensity above protesting. As far as I can tell there really isn’t.
What was I thinking of, well insurrection, domestic terrorism, sedition. But I don’t know if those are accurate.
After reviewing the definition of riot, combined with how Reuters was describing it, I revised my position. I chose to leave my comment up in order to prevent hanging replies. I attempted to defuse rather than ignore your question but apparently I can’t have that.
I have enough bullshit going on and arguing semantics on a board when I already changed my stance is not another pile of shit I would like to deal with.
Thank you.
4 Likes
Both are correct? lmao
3 Likes
the wonderful evolution of language where meanings either change or “multiply”, and eventually no one understands what eachother is saying anymore 
3 Likes
4 Likes