For over a week now, I have been trying to get Fast Ring Insider builds to work on my laptop. Failed upgrades, clean installs almost working until I notice a game-stopper like unable to install tools I need, despite whatever repair measures I take. Windows Admin Center, which I use for computer management and especially
Some users have reported their C:\Windows\Temp folder filling up with hundreds to thousands of files whose named start with “AppX.” For those so afflicted, here are some ideas on causes, and some suggested fixes.
Poking around on one of my older test machines recently, I noticed no webcam was present. This is my 6-year-old Dell XPS 2720 All-in-One (Haswell i7-4770S, 16 GB RAM, 27″ touch screen). Although I can see the webcam lens every time I sit in front of this machine, there are no internal traces of a
Windows Insider Fast Ring build 18936 was released on Wednesday, July 10. In its release notes, there was a known issue listed which seems to affect quite a few users, judging by posts on forums: A limited number of Insiders attempting to install Build 18936 may experience install failures with error code c1900101 due to
Weird! On a newer Z170 mobo PC I can’t access my dual drive dock via UASP; on an older Dell XPS 2720 it works without a hitch. Looking for clues!
I explore NirSoft’s BatteryInfoView, and learn a lot about the state of my various laptop batteries. Great tool!
A few days ago I wrote about my efforts in upgrading a Windows Insider build from 18898 to 18908 (full story). Despite several successful upgrades to new Insider builds beforehand, that upgrade failed every time. I tried everything I could think of, and everything I know, to fix this, but failed miserably on all attempts.
Until now, I have always managed to upgrade to new Insider builds on my HP ProBook 470 G5 laptop. I have sometimes had difficulties and have been forced to use various workarounds, but it has ultimately worked, every time. Last week and the release of build 18908 changed that. I did everything I could think
Because CHKDSK scans and repairs can take a long time to complete — 24 hours or longer in some cases — the question arises: “Is it OK to cancel or interrupt CHKDSK?” The short answer is yes, but it’s not a good move except in case of emergency.
Because Secure Boot blocks unrecognized software elements from loading during the boot process (before Windows starts running), it may interfere when you’re installing or updating boot-related software, firmware or drivers.