Bugfix to prevent duplicate entries for NTUSER.DAT #96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndrewRathbun
approved these changes
Jul 9, 2025
|
rebuild and staged |
|
Seems like it is all good here! Sorry again for the hassle. The joys of naming |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Made an oopsie when putting in user.dat support. On .NET6/9 it acts differently than what is in .NET4 and I assumed it was the same behaviour across both. Doing it this way prevents NTUSER .dat entries showing up twice. i.e. once for it hitting on NTUSER .dat and once for hitting the user.dat mask as well.
Sorry for this!