Page 6 of 7 FirstFirst ... 4567 LastLast
  1.    03 Jun 2015 #51
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    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

    Click image for larger version. 

Name:	WinxPower.png 
Views:	2612 
Size:	18.6 KB 
ID:	20677 Open the WinX menu
    - >Right click the Windows logon on the Taskbar


    Open the Shutdown or sign out > sub-menu


    Select Restart
    (or whatever power option you want)

    I apologize for any confusion I might have added.

    Bill
    .
      My ComputerSystem Spec
  2.    03 Jun 2015 #52
    Join Date : Jun 2015
    Posts : 28
    Win10 Preview, latest version

    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".
      My ComputerSystem Spec
  3.    04 Jun 2015 #53
    Join Date : Jan 2014
    Oak Ridge TN, USA
    Posts : 24,523
    Windows 10 Pro x64

    Never mind.. post #51 seems to work.
      My ComputerSystem Spec
  4.    06 Jun 2015 #54
    Join Date : Jun 2015
    Posts : 2
    Windows 10 10130

    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.
      My ComputerSystem Spec
  5.    07 Jun 2015 #55
    Join Date : Jun 2015
    Posts : 13
    windows 10

    Quote Originally Posted by philippetev View Post
    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.

    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!
      My ComputerSystem Spec
  6.    07 Jun 2015 #56
    Join Date : Jan 2014
    Oak Ridge TN, USA
    Posts : 24,523
    Windows 10 Pro x64

    Quote Originally Posted by brian1949 View Post
    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!
    The last two builds are leaks and I don't expect that the fix for this error will be in a build until the next official one.
      My ComputerSystem Spec
  7.    07 Jun 2015 #57
    Join Date : Jun 2015
    Posts : 2
    Windows 10 10130

    Quote Originally Posted by BunnyJ View Post
    The last two builds are leaks and I don't expect that the fix for this error will be in a build until the next official one.
    The fix has nothing to do with the fact has the build been leaked or not. If they know about the problem they will fix it no matter if the fixed build will be leaked or not. I agree with brian1949: they simply don't test the builds (at least not comprehensively).
      My ComputerSystem Spec
  8.    07 Jun 2015 #58
    Join Date : Jan 2014
    Oak Ridge TN, USA
    Posts : 24,523
    Windows 10 Pro x64

    Quote Originally Posted by philippetev View Post
    The fix has nothing to do with the fact has the build been leaked or not. If they know about the problem they will fix it no matter if the fixed build will be leaked or not. I agree with brian1949: they simply don't test the builds (at least not comprehensively).
    They do test the builds but I feel the fix for this issue will come out with an official build. And this is "testing" so there will be bugs in the builds.
      My ComputerSystem Spec
  9.    07 Jun 2015 #59
    Join Date : Jan 2015
    Spain
    Posts : 115
    Windows 8.1/10 TP 9926

    Quote Originally Posted by philippetev View Post
    Edit: the latest build 10135 seems to be affected as well.
    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!
      My ComputerSystem Spec
  10.    07 Jun 2015 #60
    Join Date : Sep 2014
    Nashville, TN
    Posts : 3,143
    Windows 10 Pro

    Quote Originally Posted by brian1949 View Post
    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!
    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).
      My ComputerSystem Spec

 
Page 6 of 7 FirstFirst ... 4567 LastLast


Similar Threads
Thread Forum
Solved Explorer crash/restart loop build 9926
Hi All I have a Dell 9150 (yes, it's pretty old!) on which I have been running all of the various W10-64 releases. Up to 9926 I have not had major issues, other than Office 2010 outlook and Word throwing CRT errors on launch. 9926 installed...
Windows Insider
Random Crash/Freeze on Build 10130
Hello everyone. I have been running the Windows 10 preview for the last few months and other than a driver issue here or there, did not experience any real problems. However, with the last update to build 10130, I have been experiencing a random...
BSOD Crashes and Debugging
Explorer.exe failure on shutdown/restart
Members with the bug Members without this bug I notice that quite a considerable number have this bug I do for one. But how many are not experiencing it
General Support
DDE Server causes continual error on shutdown or restart of Windows
Every time I shut down or restart Windows I get the following error: ----------------------------- DDE Server Window: explorer.exe Application error The instruction at Dx00007FF6D6004F97 referenced memory at 0x00000000000000BB. The memory...
Software and Apps
Solved SystemSettingsBroker Error on Restart or ShutDown
This is a new situation that I got with the update from 9926 to 10041. When I restart or shut down, as soon as the desktop closes I get this error message which I can click to Close. It doesn't occur when I Sign off. In some cases it will...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:01.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums