other things plugged in don't register at all. one other weird symptom is that my usb doesn't seem to be recognizing anything except for my keyboard.
The machine is pretty functional outside of refusing to shutdown or go into safe mode. that didn't help either still booting into normal mode. for the vstor i had to rename it, then power off, then delete it. I deleted all the files you mention in your message including the drivers. for example bcdedit reports success but no matter what i do it just boots back into windows 10 normal. It's like something is blocking the updates that change the boot config but there is no error.
i tried restoring to a restore point before the vcenter converter install. that hangs for 10 minutes and then restarts in normal mode. I tried doing the shift restart reset to restore point. i powered the machine down and it boots straight to normal mode. i tried all the other ways to get into safe mode like shift restart, bcdedit, etc. whatever i did ended up waiting about 10 minutes and then restarting in nomral mode. i discovered that i couldn't shutdown either. then it booted in to regular mode, not safe. when it rebooted, the machine hung for about 10 minutes and then reported a DRIVER_POWER_STATE_FAILURE. i used the msconfig boot tab, checked enable safe mode. I decided to boot into safe mode and see if i could uninstall. i didn't see any converter services running. the uninstall failed, saying it could not stop the service. that didn't appear to be what i needed to do so i decided to uninstall it. i thought that vcenter standalone would help do that so i installed vcenter standalone 6. Then i decided that i wanted to convert an old vm from hyper-v. the machine had hyper-v installed and so when i ran workstation it said to disable hyper-v. I installed workstation 12 pro on a windows 10 system. Thanks for posting that detailed information Plamen. The files are in "%ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone" and "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone" (+ client stuff in %LOCALAPPDATA%\VMware vCenter Converter Standalone Client")
There is nothing much interesting in registry apart from registration of these services, but if you want, see "HKCU\Software\VMware, Inc.\VMware vCenter Converter Standalone" and "HKLM\Software\VMware, Inc.\VMware vCenter Converter Standalone". These are user space processes that can be killed. The 3 services are the agent (vmware-converter-a.exe, service name vmware-converter-agent), worker(vmware-converter-w.exe, service name vmware-converter-worker), and server (vmware-converter.exe, service name vmware-converter-server).
If this is the case, check whether the conversion job has been finalized otherwise the bitmap driver starts on each machine start to keep tracking the disk changes. It starts when the machine is being used as a source of incremental conversion. Take in to account that the bitmap driver cannot be stopped once started (i.e. Those are the bitmap driver (SCM name bmdrvr) and vstor driver (vstor2-mntapi20-shared). Most probably you have a problem with one of the drivers.
Converter installation consists of 3 services and 2 drivers (excluding the client that does not register in SCM).