When Raphael Rivera tweets on potential in-app advertisements in WordPad, it gets me to thinking about ads within the Windows OS in general. For me, their absence beat their presence, hands down.
In looking at the differences between the new Feature Upgrade C:\Windows folder for Build 19546 verus its Windows.old “equivalent” (Build 19541), I couldn’t help but notice more that was different than alike. Start with the intro image for this story. Windows.old (left) includes 86,332 files and 22,148 folders and is 15.3 GB in size (15.1
Upgrade attempts to tonight’s new Insider Build 19546 failed twice when using Windows Update. Next, I tried upgrade using an ISO image made with UUP Dump. It failed, too. I am already used to working through various issues with Insider upgrades, and have some routine preparations I’ll make every time before starting. These include: disconnect
Tomorrow, January 14, 2020, is EOL (end-of-life) day for Windows 7. Starting then, only a Extended Security Contract or running Win7 as a VM on Microsoft Virtual Desktop will keep that aging OS up-to-date. Time to migrate!
With a new definition of the Fast Insider ring as a place where new Windows 10 features and functions will come and (possibly) go, the Slow ring gains importance as the focus for detailed feedback on the next planned OS release. This changes my priorities.
With the announcement for Build 19365, MS also decrees massive changes to what the Windows Insider program does and how it works. This will make life very different for Windows Insiders, so please check this out.
The Windows Insider team released Build 19536 for Fast Ring yesterday, December 16. It is the seventh release in a month. Even for keen “clean installers” like me, that is simply too many to do a clean install whenever a new build is released. However, now we can be sure that there will not be
When I see my Lenovo T520 is stuck at downloading updates, I try — and fail — to reset WU so I can try again. Catch-22! I fix it with a reboot and a disabled NIC. WU reset works, and updates begin flowing again.
In my opinion one of the characteristics of good code, be it a batch file or script or an application, is clear and precise on-screen instructions to its intended user. I recommend adding enough remarks for those reading the source code, and really doing your best to make output clear, understandable and readable. I will
OK, then: it’s official. MS announced yesterday — December 5, 2019 — that it will now automatically initiate updates to 1909 for users still running 1809. We’ve known this was coming, because EOL for was originally scheduled for May 11, 2020. Here’s the text verbatim from the Windows 10 1909 Status Page (see text outlined