Jonas L

I wondered why registry functions don't use the current transaction field from TEB the same way as filesystem operations do. I tried to force it, and now I see: That would make the use of transactions unstable. Here is why: 1/3

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

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/3

is this the place for trivia? did you know there is special location in windows? A magic place where transactions do not happen

Hmm, sounds intriguing... I remember you previously mentioned opening the entire device inside a transaction. Is there anything else? =)