Recent content by Techie007

Now running Windows 11 build 26200.9278 with 26H2 expected to release soon, yet this bug remains unresolved and bad as ever: PCs that should boot to the desktop in 20 seconds are barely usable after several minutes—over a minute for the desktop to appear after logging in, another 30 seconds...

Showing it twice is precisely the point in my first post. The OP is complaining that his local (C, D, and E) partitions are "hidden", only appearing inside of This PC, while the other drives appear outside This PC, not requiring it to be expanded to see them. But all the drives were never...

@HeavyHemi Ah, you don't have any removable drives currently connected, and all the drives are showing up normally under This PC. Plug in a USB thumb drive and you'll see how a second (duplicate) entry for just that drive shows up outside of/beside This PC. This is what the OP was referring...

It was only supposed to show your removable drives. If it ever showed your local disk partitions, something was malfunctioning. Power users hate the arbitrary duplication and clutter of the directory tree and have disabled that stupid function altogether for over a decade now using the...

Took about 8 minutes to install, reboot, and return to the desktop for me. Several of those minutes were waiting on the sluggish app launch bug Microsoft added back in June with KB5094126. Still not resolved, and still no clues in the Event Viewer as to what it's waiting for or what's going wrong.

The CPU has a new feature that causes it to downclock when inadequate voltage is present, to avoid crashing/freezing. If you lower the voltage, it will automatically lower the clock speed to match. It's part of Intel's attempts to squeeze ever tighter frequency margins out of their outdated...

Spectrum Gigabit Fiber, limited by gigabit Ethernet adapters on the router and PC (their speeds at the modem via the 2.5G Ethernet port are just over 1000 Mbps).

Personally, I just copy the profile folder to make a backup or transfer to a new installation/machine.

Yes, I'm repeatedly seeing these DCOM related errors/warnings running Windows 11 Pro (26200.8737) following startup: Warning7/7/2026 8:38:20 PMDistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID...

Sounds like something is corrupted with file associations. Processes can be created by calling the CreateProcess or CreateProcessAsUser APIs. This is how your system processes/services are getting started despite this issue. However, the shell (Explorer) doesn't use these when the user tries...

Not sure what to tell you—three different (and easy) solutions are presented in your post. You already know what to do... How are you launching ZTree? If it's via a Desktop shortcut, right-click it, click Properties, and Windows will highlight the current target for you. Just adjust it...

@spapakons Even easier than manually downloading the ISO, simply tell Windows Update to target the version you want, check for updates, and it'll download and install normally through Windows Update—even on unsupported hardware. The only one that hasn't worked for me is 26H1 (seems to ignore...

I just checked a dozen PCs running a blend of Windows 26200.8655 and 26200.8737, and ALL of them have that "Get the latest updates as soon as they’re available" toggle available. A Google search for this issue reveals it's happened before with previous versions, so between these things I...

KB5095093 (2026-06 Preview Update, build 8737) has become available. Installing it did not solve the problem, but instead increased the number of machines facing this delay issue, to where it is now affecting about half of the machines I checked. After rebooting for the update, the affected...

@NexusFred I do believe @garlin is onto something. Windows caches manifests. Where exactly, I haven't managed to figure out. Removing or replacing the manifest file will accomplish nothing once Windows has cached the contents (or absence) of a manifest. However, moving or renaming the EXE...