rl95 Posted July 2 Share Posted July 2 Faulting application name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Faulting module name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Exception code: 0xc0000409 Fault offset: 0x000000000018619d Faulting process id: 0x0x704C Faulting application start time: 0x0x1D9ACEA4A6488CF Faulting application path: C:\WINDOWS\explorer.exe Faulting module path: C:\WINDOWS\explorer.exe Report Id: bfad4427-84a6-40b6-beb3-fc32c414f3a0 Faulting package full name: Faulting package-relative application ID: Faulting application name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Faulting module name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Exception code: 0xc0000409 Fault offset: 0x000000000018619d Faulting process id: 0x0x704C Faulting application start time: 0x0x1D9ACEA4A6488CF Faulting application path: C:\WINDOWS\explorer.exe Faulting module path: C:\WINDOWS\explorer.exe Report Id: bfad4427-84a6-40b6-beb3-fc32c414f3a0 Faulting package full name: Faulting package-relative application ID: Faulting application name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Faulting module name: explorer.exe, version: 10.0.23493.1000, time stamp: 0xdf7f3ef2 Exception code: 0xc0000409 Fault offset: 0x000000000018619d Faulting process id: 0x0xD040 Faulting application start time: 0x0x1D9ACEA6F591E3D Faulting application path: C:\WINDOWS\explorer.exe Faulting module path: C:\WINDOWS\explorer.exe Report Id: 1c1f9de6-72c7-445a-9f1d-8b616b471565 Faulting package full name: Faulting package-relative application ID: Link to comment Share on other sites More sharing options...
Tihiy Posted July 2 Share Posted July 2 Try test build http://startisback.com/StartAllBack_setup.exe Link to comment Share on other sites More sharing options...
rseiler Posted July 2 Share Posted July 2 Will try it (who knew there was a separate thread on this), but I won't know for close to 24 hours if it worked or not because I just did today's workaround about an hour ago. Link to comment Share on other sites More sharing options...
rl95 Posted July 2 Author Share Posted July 2 4 hours ago, Tihiy said: Try test build http://startisback.com/StartAllBack_setup.exe Wow thanks just installed will report back in 24 hours or less!! Link to comment Share on other sites More sharing options...
markh_in_nc Posted July 2 Share Posted July 2 I just installed it too. Will check back in after 24 hours. Link to comment Share on other sites More sharing options...
rl95 Posted July 3 Author Share Posted July 3 12 hours ago, Tihiy said: Try test build http://startisback.com/StartAllBack_setup.exe So far so good! Link to comment Share on other sites More sharing options...
rseiler Posted July 3 Share Posted July 3 Yes, I'm past the period now and it hasn't recurred, so this seems good. Link to comment Share on other sites More sharing options...
markh_in_nc Posted July 4 Share Posted July 4 On 7/2/2023 at 6:48 PM, markh_in_nc said: I just installed it too. Will check back in after 24 hours. Yep... I too passed the 24 hour mark. So far, so good! Link to comment Share on other sites More sharing options...
rseiler Posted July 4 Share Posted July 4 (edited) Have any of you on 23493 noticed a parallel Explorer issue? I saw it before the test build, too, but never before 23493. File Explorer itself gets into a funk where when you try to launch it, after about a second, it closes. But then if you try it some hours later, it may work! Or not. It's very strange. I'm using XYPlorer for now. The crash dump info is different than the shell one, which was BEX64 rather than APPCRASH: Description Faulting Application Path: C:\Windows\explorer.exe Problem signature Problem Event Name: APPCRASH Application Name: explorer.exe Application Version: 10.0.23493.1000 Application Timestamp: df7f3ef2 Fault Module Name: FileExplorerExtensions.dll Fault Module Version: 723.16708.0.0 Fault Module Timestamp: 648cf049 Exception Code: c0000005 Exception Offset: 000000000007e219 OS Version: 10.0.23493.2.0.0.256.4 Locale ID: 1033 Additional Information 1: 17e2 Additional Information 2: 17e2b7babec54ed5afc192f5a9f7f471 Additional Information 3: b805 Additional Information 4: b80543948f63128ad105915805d332b7 Edited July 4 by rseiler Link to comment Share on other sites More sharing options...
karazz Posted July 11 Share Posted July 11 Fixed this problem by disabling startallback, logging out, logging in, enabling startallback, logging out and logging back in again. Problem seems to be gone! Link to comment Share on other sites More sharing options...
rseiler Posted July 11 Share Posted July 11 @karazz Are you speaking of the OP issue (corrected by the test build) or the bizarro one that I mentioned, which may be related? Link to comment Share on other sites More sharing options...
Hiroki-H Posted July 15 Share Posted July 15 The beta version you suggested worked fine. My Windows 11 is 22493.1000 Intel Core i5-8250U On 7/3/2023 at 1:01 AM, Tihiy said: Try test build http://startisback.com/StartAllBack_setup.exe Link to comment Share on other sites More sharing options...
Hiroki-H Posted July 18 Share Posted July 18 Sorry, mistake. My Windows 11 is 23493.1000 Windows 11 Insider Preview 23486.1000 (ni_prerelease) amd64 x64 2023-06-22 17:00:03 UTC ttps://uupdump.net/selectedition.php?id=f86a7451-9b1e-4d16-920b-5576e4f1ecaf&pack=ja-jp Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now