• 0 Posts
  • 75 Comments
Joined 6 months ago
cake
Cake day: June 4th, 2025

help-circle


  • The KB5066835 Windows Update, left untreated, sliced AC Shadows frame-rates from 33 percent to over 50 percent. Determining exactly which other games have been affected is not easy or obvious, mostly because Nvidia has opted not to broadcast its own findings for us to test and confirm

    But this scenario certainly has us scratching our heads as far as what kind of testing regimen and communication with GPU makers take place on at Microsoft these days. Did Microsoft’s October update expose a huge flaw in GPU drivers that OEMs needed to fix? If so, why was Microsoft unable to steward that information more responsibly to companies like AMD and Nvidia with weeks of woeful performance existing in the wild?

    It doesn’t seem realistic to me for testing to include every possible hardware configuration with every single piece software in existence, let alone varying levels of function within those software.


  • The KB5066835 Windows Update, left untreated, sliced AC Shadows frame-rates from 33 percent to over 50 percent. Determining exactly which other games have been affected is not easy or obvious, mostly because Nvidia has opted not to broadcast its own findings for us to test and confirm

    But this scenario certainly has us scratching our heads as far as what kind of testing regimen and communication with GPU makers take place on at Microsoft these days. Did Microsoft’s October update expose a huge flaw in GPU drivers that OEMs needed to fix? If so, why was Microsoft unable to steward that information more responsibly to companies like AMD and Nvidia with weeks of woeful performance existing in the wild?

    It doesn’t seem realistic to me for testing to include every possible hardware configuration with every single piece software in existence, let alone varying levels of function within those software.





  • That’s quite a headline they’ve got there!

    After provisioning a PC with a Windows 11, version 24H2 monthly cumulative update released on or after July 2025 [KB5062553], various apps such as StartMenuExperiencehost, Search, SystemSettings, Taskbar or Explorer might experience difficulties.

    This will occur for the following: First time user logon after a cumulative update was applied. All user logons to a non-persistent OS installation such as a virtual desktop infrastructure (VDI) or equivalent as application packages must be installed each logon in such scenarios.

    If you are wondering, provisioning essentially is the way admins configure devices as they automatically deploy various settings and policies on a client PC. So while the issue is in office PCs, considering a huge number of enterprise PCs are Windows, this is probably a very big problem.



  • 👋 Repair shop owner

    Between the three issues you mentioned, charge port are the most common I see with Acer whereas hinge issues are actually on the rarer side compared to other manufacturers.

    With Acer, charge ports are pretty memorable since they’re soldered to the mainboard rather than being on an easy to replace daughterboard or cable.

    Ultimately, charge ports issues are usually a user problem rather than a quality issue. There should always be extra slack on the cable when charging, the systems should be on a flat level surface, and the device should never be transported with the charger connected to the port.

    Someone who has had repeat problems related to their laptop’s charge port is going to have a real bad time if they switch to a system that uses Type C ports.


  • Or perhaps it could be something other than malice?

    This person is putting up with a misbehavior they don’t have to live with. They’re presenting the perception that it’s due to the nature of the operating system.

    My Toyota engine dies when I idle, therefore all Toyotas and fundamentally flawed.

    Flawed logic, no? And yet, when it comes to tech, plenty of folks apply the same type of thought pattern.

    You’re right that one would think the issue is as it seems on the surface. Computers are actually a bit more complicated than that.

    One fail mode of memory is the occasional bit flip silently corrupting data in the background. As time goes on and new data is written to a disk, things can get weirder and weirder over time.

    We don’t know if Windows and Linux are sharing a physical disk (I hope for their sake they aren’t) and we don’t know how old the Linux deployment is, so it’s possible it hasn’t had the opportunity to get progressively messed up enough yet.

    Another key variable is that the Linux environment might not be interacting with every single piece of hardware, or that the structure of those interactions could result in symptoms manifesting differently or not at all.

    I’ve had situations where a MacBook’s keyboard and trackpad were completely functional in Linux and Windows, but absolutely dysfunctional in any MacOS based environment. The fix? Replacement trackpad cable.

    At the end of the day, the situation they’re describing is not common for the OS and indicates something is very wrong.

    There’s plenty to complain about with Windows, but if this were a typical experience people would not be putting up with it.

    A device with those symptoms coming through my shop is statistically likely to be leaving with replaced parts, a component level repair, or at the very least a complete OS and Driver reinstallation after passing extensive diagnostic testing and behavioral isolation.






  • There is no way to ‘downgrade’ a fresh installation. Only an installation that was done as an upgrade from Windows 10 can be downgraded, it has to be done within 10 days of the upgrade and that is possible thanks to the Windows.old folder that gets retained for that period.

    In your case, you’re looking at a clean install. Once you’ve got your installation media ready, you can make your life substantially easier by using DISM to extract the drivers and integrate them into the WIM file. I’ve had a few laptops end up with no network drivers, no keyboard / touchpad drivers, and no USB drivers - leaving OOBE inoperable.