On September 30, 2014, Terry Myerson, who was then Executive Vice President of the Windows and Devices Group at Microsoft, announced the birth of Windows 10 and the Windows Insider Program. On the very next day, October 1, the first-ever public preview of Windows 10: Technical Preview build 9841 was released. A lot has changed
As MS proclaims 1903 ready for commercial deployment, I’m reminded of the old-school approach wherein businesses and organizations routinely trailed one service pack behind the current Windows release.
When an Insider machine stubbornly refuses to recognize it needs an update to the latest build, I rediscover the simple fact that a WU reset nixes insider update refusals.
Knowing that an NVMe SSD in a USB-C enclosure will be faster than an M.2 in USB 3.0, I’m tickled when the speed ratio turns out better than 3:1 for Macrium Reflect backup.
As of August 2019 NetMarketShare reports that some version of Windows 10 runs on just over one of every two PCs that firm sees on the Internet. Windows 7 share is down around 30 percent now, and dropping fast. Where will this all lead?
A certain few users have discovered that RDP connections to Hyper-V VMs work only once. If the connection is broken, one of the machines sleeps, or something similar, they are unable to use RDP to get back into the VM. Shutdown/restart of the VM is required to regain access.
Through a PowerShell command that shows available VMs inside the Fast Ring Preview, we learn that 20H1 is officially named “Windows 10 May 2020…” Very interesting!
When weird circumstances force me to reset all of my wireless networks, I’m reminded that one must set the network profile from public to private to make RDP work, too.
MS has acted swiftly to address issues with Search.UI and above-average CPU consumption rates raised from the August 26 (Release Preview) and August 30 (general 1903 release) KB4512941 Cumulative Update. In fact, the lead item in the 1903 Known Issues list (see following screencap) addresses this directly. In a previous post here at Win10.Guru (MS
As of last Thursday, MS added recently — and widely — reported issues with Windows Search to its Known Issues list for 1903. The language of the item appears in the screencap below, and makes reference both to high CPU usage and lack of search results. Given that such reports stated surfacing from Insiders on