Removing UI elements isn't access control. There will always be ways around it. Set ACLs on the actual executables so that users can't run them. THAT'S how you prevent access. Otherwise there are infinite ways around it.
Also, it sounds like you want to switch out the shell process entirely...
The desktop? The thing that's covered by my apps all the time? Why would I put anything there? The Start Menu is easy to get to on any monitor at any time.
The number of businesses out there still relying on ancient 16-bit Windows (or DOS!) applications for their line of business would depress you. And it's not like saying "use DOSBox" or "use a VM" is a working solution since plenty of them are relying on ancient hardware drivers to connect with...
Full disclaimer: I work at a Fortune 500 software company. I've also done recruiting for said company. The unfortunate reality that people don't seem to want to admit is that most Americans just aren't qualified for these jobs. If one in ten computer science graduates I talk to is worth...
The MSDN page shows you what the class returns - a Process struct. It shows you its members and methods, one of which gets the process name as a string.
That's not really the case at all....there's a large chunk of hardware that VMs don't see directly. In general, GPUs aren't directly shared, and for the most part the VM doesn't necessarily see the "real" motherboard, chipsets, etc. - they're all virtualized through different drivers.
Presumably you were running 32-bit Windows XP and are trying to install 64-bit Windows 8.1, which is why you confused the upgrade wizard (you can never upgrade cross-architecture). You can run the 32-bit version of Windows 8.1 on your CPU, but not the 64-bit version.
If you want a definitive language resource, Stroustrup is good, but if you want to actually learn the language, I recommend Lippman's C++ Primer (there are several books titled C++ primer, but Lippman's the best). My job every day of the week is writing C++ code, and while I own Stroustrup...