New
#51
This thread is too confusing - too many people posting different or the same issue.
The Explorer shutdown memory error is a bug
Topgun offered a workaround somewhere
I apologize for any confusion I might have added.
Bill
.
This thread is too confusing - too many people posting different or the same issue.
The Explorer shutdown memory error is a bug
Topgun offered a workaround somewhere
I apologize for any confusion I might have added.
Bill
.
Thanks Bill. I tried that workaround too, but the Bug is still there. I'm sure it wont be long before the next fast version is released. I haven't noticed any other problem in regards to this bug except the annoying popup. I guess the best workaround ATM with the least steps is to just click, "OK".
This issue seems to be not setup- (clean install or upgrade) or driver-related. Tried all combinations (clean install, upgrade on top on 10125, with and without the NVidia graphics drivers) and the result was one and the same (guess what!). It exists also in the latest unofficial build 10134. The workaround from post 51 worked for me. Clearly, a Microsoft issue.
Edit: the latest build 10135 seems to be affected as well.
Last edited by philippetev; 07 Jun 2015 at 08:25.
LOL now why doesn't that surprise me! - here we are weeks away from release day and all MS can do is run around like headless chickens releasing build after build (10130,10134,10135) all with such a basic error embedded in it!. They obviously don't test - just chuck out a new build and hope!
Indeed. I have tested 10130, 10134 and 10135 (all clean install) and the three of them are affected by this bug. Taking into account it's a bug that has plagued Windows in the past, I'm positively confident it'll be addressed by the time the next official build is released.
In the meantime, the Shut Down/Restart ala Windows 8.1 seems to work (or at least minimize the number of times it pops up).
Cheers!
Look, I don't mean to be rude... but Microsoft does 1 build per day, regardless of what has or hasn't been fixed. Each of these builds goes through various testing. And some of these builds get sent to partners, and occasionally leaked. That's not Microsoft "running around like headless chickens". This is just normal daily build process. How exactly do you thing we got to 10135 builds?
You act as if each of those builds was supposed to have fixed this problem. But that's not the case. Software developers prioritize bugs, and often times bugs will sit unfixed for a very long time because they are working on more serious or higher priority problems. They can't fix every bug in 1 day.
This is not a serious issue. It's not causing data corruption, or preventing people from using their systems. It only appears when shutting down, as such it's probably a very low priority, and may not even be fixed until the very last set of fixes that go into the system before code freeze... (not saying that will be the case, just that from the perspective of a software developer, this ranks very low in priority, even if to us it may seem highly annoying).