MOBO not powering down with OS Shutdown?

I can tell you what worked for me, what i did was this shutdown your PC using command. https://thegeekpage.com/fan-and-lights-staying-on-even-after-shutdown/

Progress Update:

Had a long evening last night getting all of this back up and running, but I'm happy to report that it's all working perfectly! Xhue, I can't thank you enough for your help with all of this! I ran into a few snags along the way, but managed to hack my way through most of them. Had to figure out how to convert a MBR disk (my SSD) to GPD (Thanks youtube).. Got most of my games re-loaded.. WOW.. They look amazing running in ultra with the GTX1080..

Lastly, my power down and sleep mode issues are gone.. When I power it down, it all turns off properly, as does sleep mode..

Thanks again for all of the patience!

Ah, a fellow pilot! Nice! Although I've only flew sims and held the yoke of a friend's Cessna in mid-air, I have huge ambitions getting a license myself soon.

As a pilot, you've dealt with checklists all your life, so I decided I make you another one. I hope it's easier for you.

Disclaimer: I always get giggity when flying comes out in a conversation. Please excuse my poor attempts at humor. I'll try to keep the slang at minimum, so other less-pilot(ish) people can follow too. Also, the punchlist will skip certain trivial steps for the sake of clarity.

First, some clarifications - CSM mean legacy BIOS architecture will be used system-wide, which is compatible with some older HW. Disabling it allows one to utilize the newer UEFI standard and allows for enabling some security enchancements like Secure Boot. I recommend you disable CSM.

Now, onwards unto the horizon!

- download the latest .iso from Microsoft's website.
- download Rufus portable.
- burn the .iso with Rufus.
- power down the PC.
- unplug the power cord from the wall.
- check RAM seating, cables and connectors too.
- clear the CMOS by moving the jumper in position (check manual if unsure).
- leave the CMOS jumper in its new position for some good 20 sec.
- return the CMOS jumper to its original resting place.
- plug the power cord back in the APU, err, the wall.
- plug the USB with Windows in some USB port.
- turn on the PC.
- you should hear M1 spooling up (I mean the CPU fan of course).
- enter BIOS.
- enable only XMP profile for the RAM.
- diable CSM from 'Boot' menu.
- save and exit BIOS.
- try booting from USB, aim for the option that has 'UEFI' in it.
- we're now at V1, no turning back.
- if you see Windows logo then rotate!
- if you got to this step, congrats - you almost plopped Windows.
- tune the setup options to your liking.
- after Windows is airborne, gearup that mofo, i.e. wait for it to finish with its post-install stuff (leave it alone for 20 min).
- download only AMD chipset drivers from AMD.
- download the GPU driver from their website.
- enjoy.

After all this you should have a stable and fast PC. Some additional tuning may be required afterwards, but that's also easy.

Have fun!

Once your Win 10 arrives, make sure that:

1. You check all cabling, RAM, etc. are well seated.
2. Clear CMOS
3. Enable only XMP profiles and disable CSM (you may need to ditch the DVD on boot if you want CSM disabled)
4. Plop Win 10 (preferably get the latest .iso from MS' website and burn with Rufus)
5. Download the respective drivers from nvidia, AMD, etc.

My advice - DO NOT MIGRATE any program or installation from one place to another! I can't stress this enough!

The only times you can afford direct copy/paste are portable apps, save/project data, multimedia files and VM containers. That's it.

Different OS (or builds for that matter) have (or need) different HAL settings, different registry hives (Win), different folder structures, etc.

If you old HDD has programs you no longer have the installation files, licenses (cracks?) for, that's another story. I could in theory help but most likely I simply won't.

Here is how I circumvent similar issues - on all my machines I have a disposable OS disk (not only partitions!) or disposable disk for the VM hypervisor. All the rest is hosted on networked storage. This of course cost a lot, but I put it as a goal a long time ago and boy, it was worth it! I can now wipe or lose my entire OS disk and I couldn't care less. Heck I often do experiments which end with a need for total rebuild.

Bottom line - if it's not a standalone file, re-deploy from scratch.