| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 145411 | 2017-10-26 22:54:00 | Win 10 update modifies PC hardware? | Jayess64 (8703) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1441189 | 2017-10-26 22:54:00 | I have lost count of the PCs I have built, and I thought I had started to get some idea of what goes on but this has me baffled. My desktop PC has a Gigabyte GA-H97-HD3 motherboard, about 3 years old and working well. This board has 6 SATA connectors, numbered 0 - 5, of which I have 5 in use. Last Saturday I installed the Win 10 1709 update, and everything seemed be all straight-forward with no problems. But yesterday I discovered that SATA 4 & 5 were dead, and drives connected to them gave no response and were not recognised by the system. New motherboard time? The last thing I need! It seemed a bit suspicious that this happened so soon after the update, but I couldn't (can't) think of any way updating Windows would affect the SATA connections. For want of anything better to do I went into the UEFI to check the peripheral connections. Everything looked normal; there were the 6 SATA ports all enabled and looking happy - but 4 & 5 were dead nonetheless. I felt I needed to do something, so I disabled SATA 4 & 5, saved the changes, re-booted, went back into UEFI, enabled SATA 4 & 5, saved the changes and rebooted. Bugger me! They came back to life and everything is back to normal. Can someone offer a plausible explanation of what could have happened, and why? One possible clue is that at the time of the Windows update SATA 4 & 5 had nothing connected. No.4 is used to attach a HD via a swap-rack that I use when making system backups. These are kept separately from the PC, so the drive was not iserted during the update. But I have operated like that for years and never seen anything like this. |
Jayess64 (8703) | ||
| 1441190 | 2017-10-26 23:16:00 | Pretty unlikely the OS had anything to do with that I would have thought, unless it was some queer fastboot/quick start thing that went a bit wrong during the update. | wratterus (105) | ||
| 1441191 | 2017-10-29 20:14:00 | unlikely that an OS update caused hardware issues. More likely ports 4 & 5 are using a different chipset to the intel ones and weren't detected when Windows reinstalled, so didn't install the drivers for them. | autechre (266) | ||
| 1441192 | 2017-10-30 03:13:00 | perhaps usb 4&5 are different usb type or chip not so unknown for Winupdates to screw up drivers . |
1101 (13337) | ||
| 1441193 | 2017-10-30 10:15:00 | unlikely that an OS update caused hardware issues. More likely ports 4 & 5 are using a different chipset to the intel ones and weren't detected when Windows reinstalled, so didn't install the drivers for them. Yeah, that could be right. The thread title was a poor choice of words - I really thought something on the MB had popped when the trouble first appeared. Clearly, that was not the case. ** perhaps usb 4&5 are different usb type or chip not so unknown for Winupdates to screw up drivers . ** 1101 has the same thought. One thing I have learned over many years is that all too often, when something goes wrong the cause turns out to be stupidly simple and quite obscure. |
Jayess64 (8703) | ||
| 1 | |||||