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. I don't really know what to make of this, but I'm going to go ahead and recommend not touching the toggle. Not thinking that it would work, I re-enabled SaB, and after that reboot.there's again no problem. 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. Then I thought about the CoPilot toggle, so I put that back On, but no difference, even after reboot. 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 it proceeded to happen basically every minute:Īfter the first couple of those, I rebooted but it didn't help. Within an hour or so, I noticed that the shell restarted, which was odd because I can't recall the last time that happened. 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. 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. Just in case it means something, I offer up this ambiguous information concerning 23493, the first build to have CoPilot, a major change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |