PC wouldn't boot last week, and after struggling with recov
Eery and resetting, I done a fresh install.
Windows 10 Pro, downloaded the latest version using Window's Media Install tool.
Formatted C: and fresh install. Installed some updates and installed chipset drivers. After restart the start button didn't work.
Spent hours reading 'fixes' online try to sort it, but it all failed. I assumed the chipset drivers were no longer compatible with the new build of 10, so did another fresh install.
This time I installed all available updates, sound card stuff, Chrome, LIFX app, and Office. Last night more updates were found. After installing a few and restarting, the start button is broken again! What is going on?! The settings app no longer works either, so can't continue installing remaining updates.
Does anyone have knowledge or experience to fix this?
EDIT: Also have Samsung Magician, NordVPN, and Rainmeter installed.
I rebooted in safe mode and selective startup, and the start button works in both. Rebooted back normally and it's working again. I'm thinking maybe it's a driver issue somewhere?
Eery and resetting, I done a fresh install.
Windows 10 Pro, downloaded the latest version using Window's Media Install tool.
Formatted C: and fresh install. Installed some updates and installed chipset drivers. After restart the start button didn't work.
Spent hours reading 'fixes' online try to sort it, but it all failed. I assumed the chipset drivers were no longer compatible with the new build of 10, so did another fresh install.
This time I installed all available updates, sound card stuff, Chrome, LIFX app, and Office. Last night more updates were found. After installing a few and restarting, the start button is broken again! What is going on?! The settings app no longer works either, so can't continue installing remaining updates.
Does anyone have knowledge or experience to fix this?
EDIT: Also have Samsung Magician, NordVPN, and Rainmeter installed.
I rebooted in safe mode and selective startup, and the start button works in both. Rebooted back normally and it's working again. I'm thinking maybe it's a driver issue somewhere?
Last edited: