News for hackers. Stuff that matters.
Re:Writing a Simple Windows Driver in Rust by dist-epoch on Saturday February 08, 2025 @03:48PM (#42986072)
Microsoft/Windows itself puts a bunch of junk in the home folder, and to make things worse, they have extra long names:

    ntuser.ini
    ntuser.dat.LOG1
    ntuser.dat.LOG2
    NTUSER.DAT
    NTUSER.DAT{b2352f18-cdbf-1122-8680-002248483d79}.TM.blf
    NTUSER.DAT{b2352f18-cdbf-1122-8680-002248483d79}.TMContainer00000000000000000001.regtrans-ms
    NTUSER.DAT{b2352f18-cdbf-1122-8680-002248483d79}.TMContainer00000000000000000002.regtrans-ms
Re:Writing a Simple Windows Driver in Rust by delta_p_delta_x on Saturday February 08, 2025 @04:11PM (#42986242)
These files correspond to the HKCU registry hive. There is really no better place to put them, because even the location of %LOCALAPPDATA% and %APPDATA% can be controlled... in the registry.
Re:Writing a Simple Windows Driver in Rust by dist-epoch on Saturday February 08, 2025 @04:21PM (#42986309)
they could have shorter names
Re:Writing a Simple Windows Driver in Rust by p_ing on Saturday February 08, 2025 @04:57PM (#42986531)
They're transaction log files for HKCU. Microsoft typically uses GUIDs to prevent name collisions.
Re:Writing a Simple Windows Driver in Rust by eviks on Saturday February 08, 2025 @07:02PM (#42987287)
Of course there is a better way, don't give up so easily. One immediate improvement - use a subfolder for organization, so just 1 "garbage" item instead of many.
Re:Writing a Simple Windows Driver in Rust by zamadatix on Saturday February 08, 2025 @04:09PM (#42986228)
You have to go pretty out of your way as a user to actually see those transaction logs though vs what GP is talking about with blatant pollution the user is actually expected to see and interact with.
Re:Writing a Simple Windows Driver in Rust by wink on Monday February 10, 2025 @04:43AM (#42998620)
By "go out of your way" you mean "trying to copy the contents of any "system" folder in your HOME to a new machine? :)