home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.os.windows-10      Steaming pile of horseshit Windows 10      197,671 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 195,894 of 197,671   
   Paul to John C.   
   Re: Ongoing slowing down of W10 by Micro   
   02 Dec 25 02:51:58   
   
   From: nospam@needed.invalid   
      
   On Mon, 12/1/2025 7:35 AM, John C. wrote:   
   > Lately, I've been noticing an ongoing slowing down of Windows 10 on my   
   > computer. First it was getting the Desktop toolbar I use from the   
   > Taskbar, then it was the Start Menu itself (I use Open Shell) opening,   
   > and now it's startup times for several programs that I use.   
   >   
   > After extensive discussion with Copilot, we narrowed it down to   
   > KB5068781, which applied kernel level security fixes and Secure Boot   
   > certificate updates. This could introduce extra checks during executable   
   > startup.   
   >   
   > Anybody else noticed this?   
   >   
   > TIA   
   >   
      
   I noticed some time ago (July 2025), that testing the   
   OSes and comparing them, only Windows 10 showed as being   
   slow on compute-bound things. I was using the SuperPI 1.5 mod   
   version to test.   
      
   On a test Windows 10 (on the 4930K Test Machine), when I patch   
   Win10 up-to-date (no ESU on that one), the SuperPI bench   
   does not change, and it is still slow compared to Windows 7 SP1   
   SuperPI runs.   
      
   Your complaint, could involve an ShellExperienceHost, it   
   could be DWM or FileExplorer. But that's just guesswork on   
   my part. You could use Process Monitor, to watch what things   
   happen when the slow operation is being observed.   
      
   If you are using Secure Boot for your Win10, there is   
   still a chance it could stop booting in the year 2026.   
   There was a warning about this from Microsoft recently.   
   What I noticed on the Big Machine, is no matter what   
   I tried, I could not get the 2023 certificate installed.   
   It seems something ubuntu did to UEFI, has something   
   to do with this, but I cannot be sure. If I had known   
   a Ubuntu install would be messing around in there, I never   
   would have run it there.   
      
   The only thing I haven't done on the Big Machine, is   
   used the UEFI factory reset. There are tales of brickage from   
   doing such things, so I'm more than a little hesitant to   
   be messing around. The likely result, is Secure Boot   
   will be turned off on the Big Machine for good.   
   No more experiments with Secure Boot.   
      
   *******   
      
   And in totally unrelated news, I got another hint yesterday,   
   about what the problem is on my daily driver.   
      
   I was typing away, I brought some window to the front.   
   The window stopped responding. I looked down, and my mouse   
   LED was off, and the shift key didn't work on the keyboard.   
   The bloody machine had turned off the +5VSB to peripherals   
   again.   
      
   Now, normally when that happens, I'd be pressing Reset   
   and rebooting it. And the log would note a dirty shutdown   
   and no error recorded.   
      
   Well, this time, something different happened. A watchdog   
   timer went off. It seemed to be the NVidia driver that   
   was involved (daily driver uses a GTX1050 to drive the screen,   
   a low end video card). The driver actually recovered. And,   
   it seemed to send a report to Microsoft (there was network   
   activity).   
      
      Problem signature   
      Problem Event Name:    LiveKernelEvent   
      Code:   1b8   
      
      Extra information about the problem   
      Bucket ID:   LKD_0x1B8_NV_Blackscreen_Blackbox_dxgkrnl!DxgCre   
   teLiveDumpWithDriverBlob   
      
   Now, why would a driver failure, cause the power to my PS/2 keyboard   
   and USB mouse, to be turned off ?   
      
   And before the GTX1050 went in there as a bandaid,   
   this was happening with the AMD iGPU in the processor.   
   That iGPU is turned off now, as I'm using a video   
   card instead. And this problem does not show   
   on the other machines.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca