mikeymikec
Lifer
- May 19, 2011
- 20,109
- 14,586
- 136
JackMDS and deustroop do seem to be wilfully misconstruing what Craig234 is saying. I'm pretty sure that Craig234 is asking whether 1607 is worth the potential trouble to install and what the potential troubles are likely to be for people who upgraded.
I haven't seen an awful lot that 1607 fixes first-hand. I thought it was silly that in Win8x and 10 (pre-1607) that if Windows Defender was enabled, it didn't have a systray icon, and 1607 fixes that.
One undeniable fact is that pre-1607 will stop being supported with security updates at some point sooner rather than later.
I'm not aware of anything that 1607 breaks in general. On one customer's very low-end laptop, 1607 installed an "updated" and buggy graphics driver that made the machine pretty much unusable, but that's all I've experienced. This was potentially extremely problematic as AMD's drivers for this device were mostly exhibiting the bug and I had configured the machine to use the original driver that Win10 shipped with. As that driver no longer works on 1607, it was fortunate that AMD had finally pulled their finger out and released a working driver for the device in question (an APU for an AMD C-range CPU IIRC, or maybe an E2 something-or-rather, IIRC Radeon HD 8210).
To fix the broken update, if you have plenty of time, I'd do this in order:
In WU options, disable update retrieval from other sources, try installing the update again. If that doesn't work:
chkdsk C: /f /v /r
reboot, disk check completes
sfc /scannow
if it says anything remotely negative (e.g. "found issues and fixed them") reboot
dism /online /cleanup-image /restorehealth
if it says anything remotely negative (e.g. "found issues and fixed them") reboot
Try installing the update again
If you have less time, skip the chkdsk and leave that as a measure of desperation.
In case it needs saying, I don't see any good general reason to avoid 1607, I only see good reasons to upgrade. If however there's a greater risk due to something specific about your machine, that's certainly relevant to you and you ought to ask about it.
I haven't seen an awful lot that 1607 fixes first-hand. I thought it was silly that in Win8x and 10 (pre-1607) that if Windows Defender was enabled, it didn't have a systray icon, and 1607 fixes that.
One undeniable fact is that pre-1607 will stop being supported with security updates at some point sooner rather than later.
I'm not aware of anything that 1607 breaks in general. On one customer's very low-end laptop, 1607 installed an "updated" and buggy graphics driver that made the machine pretty much unusable, but that's all I've experienced. This was potentially extremely problematic as AMD's drivers for this device were mostly exhibiting the bug and I had configured the machine to use the original driver that Win10 shipped with. As that driver no longer works on 1607, it was fortunate that AMD had finally pulled their finger out and released a working driver for the device in question (an APU for an AMD C-range CPU IIRC, or maybe an E2 something-or-rather, IIRC Radeon HD 8210).
To fix the broken update, if you have plenty of time, I'd do this in order:
In WU options, disable update retrieval from other sources, try installing the update again. If that doesn't work:
chkdsk C: /f /v /r
reboot, disk check completes
sfc /scannow
if it says anything remotely negative (e.g. "found issues and fixed them") reboot
dism /online /cleanup-image /restorehealth
if it says anything remotely negative (e.g. "found issues and fixed them") reboot
Try installing the update again
If you have less time, skip the chkdsk and leave that as a measure of desperation.
In case it needs saying, I don't see any good general reason to avoid 1607, I only see good reasons to upgrade. If however there's a greater risk due to something specific about your machine, that's certainly relevant to you and you ought to ask about it.
Last edited: