Recurring issues in Windows 10 Pro 64 bit

System info: Intel motherboard DH67CL with Intel i5-2400 quad core processor. 8 Gb RAM. Self built in Cooler Master tower.

These issues keep recurring regularly.

Bootup: Frequently takes just over 2 full minutes to boot. Work around is to restart using restart button on tower, after Intel info screen appears, which reduces time by 90 seconds. Very annoying.

Shutdown: Frequently turns off monitor display, but PC keeps running indefinitely. Need to perform hard turn off, or turn off mains power. Ditto very annoying.

Safe removal of USB devices: Frequently, using either drop down menu from USB device shortcut, and choosing eject option. Or safe removal on Notification area. Error message comes up: "Device is currently in use. Files could be damaged. Cancel. Try again. Continue." By clicking Try again, it shuts down and have never had any file damage. But what's annoying is the USB device was not open, but closed.

Drag/drop folders/open files: Almost always the mouse pointer has to be placed on the top bar of the file, and left click held down for 4 or 5 seconds before the file can be dragged/dropped. Very, very annoying as this feature is frequently used for filing purposes, etc.

eSATA socket: After every update, the eSATA socket fails to read the docking station for spinner hard drives. Usually it can be fixed by running Troubleshooting in Control Panel, which updates drivers. But last time this failed and it only worked after installing "Intel Rapid Storage" onto Win10. Other times it only worked after running the hard drive on Win7 eSAtA, and right clicking the hard drive icon in Computer > Properties > Tools > Check drive for system file errors. It then worked in Windows 10 eSATA port, but the check drive was not originally available in Win10.

I hope the administrators of Windows Insider rad these posts.

Hi Mustang.

Please take a moment to fill in system specs, especially Motherborad and Version Build numbers.

Safe removal of USB devices, I see this all the time. Not sure why but in my experience it is the larger drives. 8GB and below eject fine. I have a 64GB and it will be a cold day in H377 when that ejects properly.

The other items to me sound like drivers. In particular Windows is loading default drivers and not system hardware specific. The last item is a great example, it has to install Intel Rapid Storage. I would scan device manager and ensure the right drivers are being loaded, like the one for your mouse, not the one that sort of works. You may need the Intel Management Engine. I would see what the vendor has listed on their site and then look to see how your system is handling.

If this is drivers then document and store the ones you need, every major update you will need to do over.

The very first issue, bootup, sounds like Windows Fast Startup isn't processing right, especially if you have to hit the "Reset" button on case.

To a command prompt(admin) or powershell(admin)

powercfg -h off

This shuts off hibernation which quickly disables Windows Fast Startup. If this works you can renable hibernation, same command but with the word on, and then just kill Fast Startup.


Ken

Interesting. the initial boot for sure sounded like Fast Startup.

If you could, Windows key + R, type winver, enter. It will likely say V1607, OS build 14393.xxx. Could you post please?

Have you run sfc /scannow ?

Not say to do it but are there any BIOS updates posted on your motherboard web site?

Have you tried going into Advance Power options and restore defaults for current plan.

Great. So it is drivers. One thing to watch when you install a driver and it works for a while. Go into device and note driver you installed, then when you feel it is not working check driver version.

Windows is set to update drivers automatically and it sounds like it is not identifying your gear correctly or you wouldn't have to install the Marvell driver.

Somewhere down in the bowels this could be 'influencing" other items like power.

I found this article and this is what I'm using in 1703. It must be working as my Wi-Fi card requires an ancient driver and I know there are current updates, I get the most recent one every major update, like V1703.

https://www.howtogeek.com/302595/how...dware-drivers/

In the article quite a ways down there is a link labelled “Disable Automatic Driver Updates Hacks”
This downloads a zip file with two registry hacks. Read the paragraph above the link. I used the hack on my V1703 (Creators). Likely have to run Hack after each major update, Anniversary, Creator.

At some point your device is going to update to Creators (V1703), you are on Anniversary (V1607). When this occurs check on those Marvell drivers. Bet they are gone and issues will be back.


Ken