Jump to content

rseiler

Member
  • Posts

    94
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by rseiler

  1. 19 minutes ago, thepwrtank18 said:

    0xc1900101 is an unrelated issue. MS screwed up the bootloader for the new installs, so it just keeps reverting.

    Oh, I guess that's good, but I wonder how I got so lucky since a lot of people have installed the build successfully (not counting the SaB problem, I mean). Has MS admitted to this somewhere?

  2. Anyone get to 26100 successfully with SaB?  WU just reboots right back into Windows for me and reports a WU error of  0xc1900101. I've never seen SaB cause that before, but considering the above dialog (which I didn't see because I wasn't doing an ISO-style update, which I assume is what that was from) I have to consider the possibility. Retrying it a couple more times yielded the same result. Am on 3.7.8 (26090).

    Update; If this is because of SaB, it would be pretty puzzling since it also occurs after disabling SaB.

  3. I guess I'll soon be seeing how well this works with Canary these days, even though I'm in Dev. Dev has been moved up to the same level as Canary (26052). Canary will stay on the same track as Dev for a while (giving people a chance to easily change channels to Dev if they wish) before it shoots ahead to a higher series in some unspecified future week (I would guess at least a couple weeks from now).

    Update: What we've seen be a sticking point in the past is the vertical toolbar, but that is not a problem. I initially thought it might be, since it was switched to horizontal (even after I thought I clicked Enable, as usual, post build update), but I went into Control Panel to enable it there, and once the shell restarted it was fine.

  4. 10 hours ago, Tihiy said:

    They don't.

    The two I initially looked at do, but beyond that what does it mean relative to the feature that we're talking about that the same app can have different IDs at different times? I know for sure that it's the same app because of the 2008 thing.

  5. On 12/4/2023 at 10:15 AM, Tihiy said:

    HKCU\Control Panel\NotifyIconSettings

    Ah yes, thanks. In coming from 3.6.last to 3.7.1, I noticed that my clipboard program was listed 6 times in the Tray Icons menu, but I found them there in the reg to delete. I suspect this is because they had distinct "InitialTooltip" (given that the clipboard program puts what you're copying to the clipboard in the tooltip),  but that's just a guess. 

  6. That pic a few posts above, of 15 or so tray icons, reminds me to ask: are there any plans in 3.7 to keep track of whether those are hidden or not? The reason I ask is that information is lost when you do a Windows build upgrade, which some of us do about 50 times a year. It would be almost magical at this point if SaB could have its own system for keeping track of them so Windows doesn't screw them up every single upgrade.

  7. 7 hours ago, Tihiy said:

    StartAllBack 3.6.16

    3.6.16 will update to 3.7BETA if checked.

    I assume you mean if "Check for updates" is clicked from 3.6.16? At first I thought this might be a reference to a check box which would opt someone into the beta from this release, but I don't see one.

  8. Was anyone shunted to a Windows setup screen about continuing to use facial and fingerprint recognition (neither of which I use) when upgrading to the .15 release? I've never seen that screen before, so it was a surprise. I chose one, since there seemed to be no other choice, clicked Next, and it then opened Settings, Accounts, Sign-in options.

    23570

  9. 6 hours ago, T. BugReporter said:

    And speaking of annoyances, with my latest W11 update, I got a new icon on SaB's taskbar with a tooltip saying "Copilot (preview)" that launches Edge (not my default browser) when clicked.  Oddly, it doesn't appear when I turn off SaB.

    Is that in Dev? At least there, I haven't seen Copilot at all, perhaps because I have it disabled in group policy (User Config, Admin Templates, Windows Components). There would also be an equivalent Registry mod to do the same for those without gpedit.

  10. 12 hours ago, T. BugReporter said:

    Not likely.  Most Windows files are digitally signed now; any attempt to patch them would be detected as an attempt to inject malware.

     

    There's a very, very long history of patching termsrv.dll successfully. If done right, the only thing the OS does is replace it on the next Patch Tuesday (assuming that's one of the files updated that month).

  11. Suggestion: Upon installing a new Windows build, SaB triggers a notification telling us that there is no new version (of SaB). It would probably be better to only trigger that if there is. since otherwise it's a notification of nothing, which isn't normal.

  12. I'm on that build. While I don't have any desktop items to right-click, note that a workaround for the CP issue would have been to access it in Start via the Menu display option, as that worked. As did accessing it via a right-click on Start (if you have that configured, which is not a feature of SaB). It probably would have run via Start/Run/control.exe, too, though I'm not sure about that one.

  13. Unsure if it's a 23xxx problem or the SAB test build (using the one with the July 9 signature), but selecting "Pin to Start Menu" for an item in the Start Menu actually pins it to the taskbar instead, as if you chose "Pin to taskbar."

×
×
  • Create New...