I actually did this over the weekend with Minitools Partition Wizard, although considering it’s messing with your entire drive, it would be highly advisable to make sure everything is fully backed up before doing it.
With the built in Windows disk-management stuff I had to shrink the primary volume of the MBR drive by like 600-700MB or so to make room for the extra volumes required, so there’s some unallocated space. If you can’t do that ahead of time, I assume you might be able to do it during the main conversion, although when I attempted that it appeared to just freeze (although it might have eventually resolved if I’d left it).
After that, I used Minitools Partition Wizard which has like an inbuilt option to do it. Although I was doing it in Windows, and then it reboots since it was my main drive and does the conversion in its own little boot environment thing.
I would assume you can use their boot media tool to do it all in their own boot environment if you can’t even get into Windows to at least start the process.
So it definitely appears to be some sort of memory-leak, although tracking down exactly what is causing might be a huge pain since the “Session Private” area where the memory-leak appears to be happening doesn’t appear to easily be tracked as to which process is causing the growth.
Based off a post on StackOverflow, it might be worth downloading Process Explorer, then enabling the ‘Handles’ column and seeing if there’s any process that slowly grows over time and reaches some absurd number of handles. You may need go into the File menu and elevate the program to admin privileges under the ‘Show Details for All Processes’ option for it to give proper details for everything including system processes.