Answered
This topic is locked
OK this is one for all of the guys on here who came on about a year ago or so 'screaming' at me and trying to force me to reinstall my Windows 8, over what was a relatively minor, although no less anoying bug at that time. These guys practically accused me of "lying" and denied that any such bug could possibly exist - and even though it was a very small/anoying bug, for the vast majority of them the only possible solution was to 'reinstall windows'. Clearly they imagined because they knew how to do this, this made them 'tech experts.' Never mind the fact that reinstalling windows is as best a basic skill that requires almost no knowledge at all, or the fact that reinstalling windows has been shown in many cases not to be effective in this bug. Nor it seems did the concept of 'sticking with a problem' and 'troubleshooting' in order to get to the bottom of it, seem to have any meaning to them. You learn nothing by reinstaling, even if sometimes it might seem faster.
Anyway, that's all water under the bridge. The reason I am here today is to report that I have now resolved this problem on the affected system 100%. Yes it took nearly a year and a lot of persistence and a lot of effort, but hey I learned something useful in the end.
To understand this bug you can look here:
https://social.techn...forum=w7itproui
and here:
https://encrypted.go...lorer windows 8
which all in all is a llot of chatter about a bug a lot of people on here implied was a figment of my imagination. However it was the technet thread above that finally caught my attention. On here I found two possible solutions I had never seen before.
These were:
"Turn off Windows write-cache buffer flushing", by Noel Carboni at the start of this thread and the registry key fix proposed by user Lurkout:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Update] "UpdateMode"=dword:00000000
I won't go over them all again here as they are both on the first page of this thread, my pupose here is simply to point anyone else who is stumped and who is looking for a solution to this problem in the right direction. Apparently there's no reason why the second of these fixes should work, as "UpdateMode" has something to do with group policy (second hand information, so I'm not sure how accurate this is), But anyway this seemed to do the trick for me. In my case there was a slight variation in that as my sytem is 64 bit I used a qword instead of a dword, but all the same it worked fine. (After a reboot).
I also tried the first fix and then forgot I had done this, so to be fair I am not certain at this time which of these fixes was responsible for sorting this issue. But at least I have a much better clue than I did before. I have also included the first fix as it seemed to deliver a significant performance boost, as my system has gone from a two year windows install type sluggish, to almost 'snappy' after this setting was enabled. It might not be safe on desktops without UPS, but on laptops (particularly if they are set to hibernate on low batttery power) or UPS enabled systems, it should be fine.
Of course this fix might not work for everyone, but that thread is packed full of possible solutions, so well worth a visit anyway. My guess is that this probably will work in most cases however.
Anyway, like I said, every day you learn something new.
