Build 10130 - explorer.exe crash on shutdown or restart

Page 6 of 7 FirstFirst ... 4567 LastLast

  1. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #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

    Build 10130 - explorer.exe crash on shutdown or restart-winxpower.png 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 Computer


  2. Posts : 28
    Win10 Preview, latest version
       #52

    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 Computer


  3. Posts : 22,740
    Windows 10 Home x64
       #53

    Never mind.. post #51 seems to work.
      My Computer


  4. Posts : 2
    Windows 10 10130
       #54

    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 Computer


  5. Posts : 13
    windows 10
       #55

    philippetev said:
    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 Computer


  6. Posts : 22,740
    Windows 10 Home x64
       #56

    brian1949 said:
    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 Computer


  7. Posts : 2
    Windows 10 10130
       #57

    BunnyJ said:
    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 Computer


  8. Posts : 22,740
    Windows 10 Home x64
       #58

    philippetev said:
    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 Computer


  9. Posts : 131
    Windows 10 PRO for Workstations
       #59

    philippetev said:
    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 Computer


  10. Posts : 3,257
    Windows 10 Pro
       #60

    brian1949 said:
    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 Computer


 

  Related Discussions
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 09:05.
Find Us




Windows 10 Forums