NTFS deals with potential conflicts by blocking actions that introduce them, so an external caller cannot interfere with a transaction in a way that prevents its merging. 2/3
-
Show this thread
-
Configuration Manager, on the other hand, aborts the entire transaction without notice. If someone modifies a related key, even when it shouldn't cause a conflict per se, it results in a complete loss of progress. Sigh.
3/31 reply 0 retweets 0 likesShow this thread -
Replying to @diversenok_zero
is this the place for trivia? did you know there is special location in windows? A magic place where transactions do not happen
1 reply 0 retweets 0 likes -
Replying to @jonasLyk
Hmm, sounds intriguing... I remember you previously mentioned opening the entire device inside a transaction. Is there anything else? =)
1 reply 0 retweets 0 likes -
-
Replying to @jonasLyk
Yeah, nice job, I saw this one. Though, my knowledge of NTFS internals is not enough to figure out how you managed to make it work =)
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
-
Replying to @jonasLyk
Okay, I managed to create a process from a file under
$txfLog. Why does yours show this weird image name? Is it because you named it with three dots?pic.twitter.com/AYLoIPK1VJ
1 reply 0 retweets 0 likes -
Replying to @diversenok_zero
i rename it to that, windg sees the filename as the symlink that launched it. ph show original name some place, renamed into others
1 reply 0 retweets 0 likes
Jonas L Retweeted Jonas L
i could also combine with thishttps://twitter.com/jonasLyk/status/1359584139004026885 …
Jonas L added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.