Windows 8.1 Pro x64 UEFI very slow boot and shutdown

I have a "new" HP Envy and the startup is fine but the shutdown takes about 4 minutes.  Have run also run ccleaner and superantispyware and the shutdown was fine for one time but then went back to the 4 minute shutdown.  Also tried reinstalling a couple of the programs to see if that helped.  Nothing.

I have a "new" HP Envy and the startup is fine but the shutdown takes about 4 minutes.  Have run also run ccleaner and superantispyware and the shutdown was fine for one time but then went back to the 4 minute shutdown.  Also tried reinstalling a couple of the programs to see if that helped.  Nothing.

A lot of people have solved this problem by uninstalling the factory drivers for the Qualcomm Bluetooth and wifi card.   When you reboot, Windows will supply generic drivers that work fine and boot and shutdown times go back to normal, very fast, like Win 8 before the upgrade.  The problem is the next windows update you get will want to re-install the factory drivers and you  have the problem back.  Be sure to watch out for that and don't install but "HIDE" the update.  I have heard that Qualcomm may have updated the drivers but I am sticking with the generic ones that I know work with 8.1

Tess82e        replied on    

-

Hi, for me the thing that causes this is the Bluetooth-device. Disabling it in Device Manager makes Windows go back to 10 s shutdown, as before 8.1. 

In my case the device is Qualcomm Atheros AR3012 Bluetooth 4.0 + HS. Maybe new device drivers will solve the problem.

Believe me guys I had faced this problem for about an year I hated to install updates and everything which causes my laptop to restart because it was really painful to watch a near about 5 minutes of restart. I REPAIRED my windows many times (more than 5 or 6 times) in this interval but problem did not go.

But I figured out while repairing windows who was the culprit by installing one application and driver and then restarting to test it and I found out that DIRECT Xwas the culprit. I don't know why but I think it was interfering with AMD Graphics card driver.

I finally completely reformatted (remember this time I did not repaired but re installed from scratch) my windows partition and then installed direct x first (from online installer and not from offline or standalone installers), then other drivers and applications and it worked out magically.

Also I would like to point out that repairing windows will never work in this situation only reformatting will do.

ADVICE- Do not install directx until you need it. It is only for gaming and some designing softwares. 

Earlier my normal shutdown time was about 3-4 minutes but now it has reduced to 20 seconds.

Guys lease try this and reply your results.

Ever since I upgraded to Windows 8.1 via the in-store update my PC takes a good 3-4 minutes to boot!!! I am on a GA-X79-UD3 + i7-3820 + Samsung SSD 840 for system drive. I have updated all my drivers to Windows 8.1 compatible ones and still. I have checked via Samsung Magician and the drive is using AHCI mode on (Intel PCH) Sata 3 6Gb/s.  I have tried restoring my UEFI to default settings and enabling Fast Boot but still?? On Windows 8 it would boot in 5 seconds....

EDIT: Have tried Safe Boot and Clean Boot, still same

EDIT2: Will any Microsoft guy chime in?

Ever since I upgraded to Windows 8.1 via the in-store update my PC takes a good 3-4 minutes to boot!!! I am on a GA-X79-UD3 + i7-3820 + Samsung SSD 840 for system drive. I have updated all my drivers to Windows 8.1 compatible ones and still. I have checked via Samsung Magician and the drive is using AHCI mode on (Intel PCH) Sata 3 6Gb/s.  I have tried restoring my UEFI to default settings and enabling Fast Boot but still?? On Windows 8 it would boot in 5 seconds....

EDIT: Have tried Safe Boot and Clean Boot, still same

EDIT2: Will any Microsoft guy chime in?

Sorry to tell you this but you are not going to get a MS person to respond because it is not a MS problem. Read through this thread for the solutions most people have found. I and others found it is a driver problem that has not been properly updated by the supplier of the driver. There is no one magic solution and you have to find the offending driver yourself.