rseiler
Content Type
Profiles
Forums
Events
Posts posted by rseiler
-
-
Yes, I'm past the period now and it hasn't recurred, so this seems good.
0 -
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.
0 -
Just in case it means something, I offer up this ambiguous information concerning 23493, the first build to have CoPilot, a major change. For the record, I'm on SaB 3.6.8.
I had been running 23493 continuously and without incident for almost 22 hours when I happened over to Taskbar Settings and noticed CoPilot toggled On. Since I'm using SaB, there was no obvious presence of CoPilot, and I didn't want it anyway, so I toggled it Off without a second thought.
Within an hour or so, I noticed that the shell restarted, which was odd because I can't recall the last time that happened. Then it proceeded to happen basically every minute:
They look like this:
Example dmp: https://www.upload.ee/files/15396774/explorer.exe.5796.7z.html
After the first couple of those, I rebooted but it didn't help. Then I closed everything I had been running (even though they were the same things I'd been running the last day), but no difference. Then I thought about the CoPilot toggle, so I put that back On, but no difference, even after reboot.
So now I tried disabling SaB and it stopped happening, which was interesting, since why wasn't SaB a problem the first 22 hours? The only thing I can think of is some kind of strange (and delayed) CoPilot interaction, but I can't prove it.
Not thinking that it would work, I re-enabled SaB, and after that reboot...there's again no problem. I don't really know what to make of this, but I'm going to go ahead and recommend not touching the toggle.
Update: The above-mentioned rapid-fire shell crashes seem to trigger roughly every 24 hours, which I think explains why I didn't see it happen until around that amount of time in the first place, and why it went back into that mode a day after what I wrote above. It's perhaps objecting somehow to the presence of SaB at that interval, but if you play around with the toggle and temporarily switching SaB off, you can get back to a stable state (with SaB), though I'm pretty sure just for a day, when it all repeats.
Update 2: In today's iteration I did this, which I think is the essence of the workaround, since don't forget that the problem starts because Windows can't do something that it needs to do:
-Restarted the shell myself and used the ESC method to prevent SaB from loading.
-Waited a couple minutes for Windows to do whatever it needs to do.
-Restarted the shell so that SaB loads
0 -
@Manoes Wow, so you figured out that reverting to a build from 7 April 2022 (!) stops that window position problem from being one? Not sure how you did that, but I guess that's one way of showing SaB's involvement. I can't remember when the problem started, exactly, but a year ago is reasonable, though if you said two years ago, I might think that reasonable too. It's been too long either way.
0 -
@Manoes It's not just Explorer. It's most programs that I use, though much more position than size. Is that related to SaB though? If so, I didn't realize that, but I also haven't tested without it. Using this makes it less of a hassle:
https://github.com/caoyue/WindowResizer
I wish we had something similar for the tray icons all being hidden with each build upgrade. I've been experimenting with backing up and restoring these two areas, but no joy so far. I have no idea if it's even valid to do this between builds:
HKCU\Control Panel\NotifyIconSettings
HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify
On the good news front, SaB 3.6.4 has an unannounced feature: it doesn't throw a build warning (i.e. disabling itself and making you re-enable) for 23xxx anymore.
0 -
On 4/14/2023 at 7:28 AM, TheInvoker said:
how do i stop the request for updating to a new version?
4 hours ago, Tihiy said:You can't and shouldn't.
Is the same mechanism used for the build compatibility check, which results in SaB being disabled, the boot halted, and then the user being required to answer a question about whether they really want to run SaB?
If so, then "can't" would answer that question, too. If not, the question of whether there's a way to prevent the above remains.
0 -
Is there a way to suppress the Windows build check? Because if there is, perhaps via the Registry, it would be nice if that was revealed.
0 -
I'm not sure what 9/10 means, but yes, I'm talking about the SaB dialog that comes up very early after a new build install warning you about running it and essentially requiring you to opt-in if you want to run it. If that was meant to happen, it should have happened when going from 23403 to 23419, too. It definitely did not then, and that was just a week ago.
0 -
Though come to think of it, it didn't happen for earlier 23xxx, as I'd never seen this before, which makes me wonder which behavior is intended.
Also, the timing of it, which was pretty early in the boot, may have contributed to the fact that the keyboard didn't work until after another reboot. Might have been a fluke, but I'd never seen that before either.
0 -
Is it expected that SaB 3.6.3 should display a compatibility opt-in warning message after a build upgrade to 23xxx (seen with 23424)? If so, is there a way to make it just opt-in by default and not ask? It's probably warranted for 25xxx but arguably not 23xxx.
0 -
Yeah, it looks like taming PastIconsStream and IconStreams, at the very least. Probably iffy.
0 -
Yes, I had the same idea. Finding where it is shouldn't be too hard.
I'm beginning to wonder now if I was actually using SaB back when I was doing build updates every week (before recently, I mean), and perhaps I wasn't (time flies), which wouldn't make this a recent change at all.
0 -
Does SAB have any involvement with remembering whether a system tray (notification area) icon is shown or hidden?
I ask because I've noticed when going to 23403 and now from 23403 to 23419, that almost all of them are hidden. Yes, dragging back out the ones you want works, but this will reset again with the next build upgrade.
While I do know that this never used to happen in previous years, I haven't been doing build upgrades in recent months to be able to narrow when it started--or even if SaB has anything to do with it.
Using 3.6.3
0 -
Given the new channel situation, has anyone tried the first 23xxx build (23403) yet, which is the first build on the new Dev channel? I know Dev wasn't recommended for use with SaB in the past, but Canary is really what Dev used to be (even more so), and the new Dev is like a slightly more aggressive Beta channel and is thought to be the 23H2 track. Before, Dev wasn't necessarily on any track, it was more for feature experimentation, like Canary is now. This all seems to suggest that new Dev might generally be OK with SaB, certainly more than old Dev. What do you think?
0 -
In case it's relevant, I noticed this crash, seemingly out of the blue and isolated in the sense that I don't recall it happening before:
QuoteDescription
Faulting Application Path: C:\Windows\explorer.exeProblem signature
Problem Event Name: APPCRASH
Application Name: explorer.exe
Application Version: 10.0.22621.755
Application Timestamp: bcd85d13
Fault Module Name: StartAllBackX64.dll
Fault Module Version: 3.5.4.4550
Fault Module Timestamp: 636e2f35
Exception Code: c0000005
Exception Offset: 0000000000044c26
OS Version: 10.0.22621.2.0.0.256.4
Locale ID: 1033
Additional Information 1: 2f14
Additional Information 2: 2f14026323dbac101795c3a7bf80623a
Additional Information 3: 135e
Additional Information 4: 135eafc6d7c5f6fdb2248552789ee43b
0 -
Is the dragging up or down of pinned items in Explorer (Quick Access section) supposed to work with SaB, at least on 22H2? It looks like you can drag them, but nothing happens.
Seems to work fine in Sandbox, which of course is vanilla 22H2.
0 -
6 hours ago, Kleine Eule 73 said:
If "Use small taskbar buttons" is checked in the taskbar properties, no date is displayed, only the time.
If this checkmark is removed, the date is displayed in the taskbar.
You mean this setting? It doesn't seem to exist in the UI any longer, and it's not one that I've changed in recent memory in any case.
https://www.tenforums.com/tutorials/25233-use-large-small-taskbar-buttons-windows-10-a.html
But I checked TaskbarSmallIcons: it's on 0.
Update: After playing around trying to figure this out from the perspective of another install (also with a vertical toolbar, which I think is key to seeing this problem), I found that if I unlocked the taskbar and made it slightly wider than it had been that the date then appeared. I'm not exactly sure if something in this area changed with 22621.608, but instead of leaving it wider I put it back to its normal width and went into calendar settings in Control Panel to set "Short date" to "M/d/yy" from "M/d/yyyy." That takes up much less room so it fits fine now.
0 -
Wondering if this is just me, and if not, if there's a way to correct it. The time but not the date is showing directly on the taskbar (unless you hover over that area) when it used to show both.
SaB: current
W11: 22621.608 (it's possible that it started with this version, since this issue is fairly recent, but I'm not sure).
0 -
3 hours ago, Horst said:
There will be a Windows 11 update which brings back this missing functions
and then there is no more a need for this tool.You have great faith. When the Windows team over the course of nearly a year ignores the #1 request, and doesn't even talk about, it's not a great sign. And there are more where that came from.
0 -
Hi. I have the latest version on 22000.613, but the problem I've noticed started a couple months ago. I didn't think anything of it at first, because it doesn't happen most of the time, but I thought I'd ask here:
Every once in a while, when I go to run something on Start (and I'm just talking about top-level things immediately visible), when I click the item it takes perhaps 5 seconds to launch whatever it is. That's not normal, since it's usually instant.
I thought it might be Defender playing games, so I was going to make an exception for Startallback in Defender, but I don't actually know that that's even possible, since there doesn't really seem to be a Startallback process to make an exception for. Or is there?
0 -
On 4/7/2022 at 9:09 AM, VitalS said:
Is there a way to enable only the Win 10 calendar with a big clock flyout, but the rest is left as it is?
What is the rest? I just compared the two, and aside from the useful addition of the time in the Win10 one (the only place you can see seconds), they're all but identical.
0 -
Just curious, with the great Control Panel migration continuing:
https://www.ghacks.net/2021/12/18/microsoft-migrating-windows-control-panel
Are we also affected or are they not truly gone? I'm not on the Dev build, but of course that change is coming for mainstream Win11 eventually.
0 -
I thought the same thing about public=Public when first going through the settings, and I see now that I did uncheck it for that reason. So, in my case it doesn't matter for search in my profile, which is in the default location.
So, I'm not exactly sure what to think, but I think it's safe to assume that something wasn't accounted for with that setting relative to your uncommon scenario.
Does MS still consider that an "unsupported" config, btw? I think at some point such a relocation caused big problems when it came to Windows upgrades, but that's a bit hazy now.
0 -
Interesting. Since I've never seen this, and it's not an underlying issue (i.e. doesn't happen without SaB), is it possible that it relates to a particular combo of SaB settings that I don't have? Maybe try "Set default values" in SaB's Start menu config area, though I don't know how comprehensive that is?
BTW, 3.1.2 just dropped, so give it a try.
0
Explorer crashing every minute on latest insider Build 23943
in StartIsBack+
Posted · Edited by rseiler
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