Subject: General Tech | April 6, 2017 - 12:46 PM | Jeremy Hellstrom
Tagged: powershell, cmd, windows 10
One thing you may notice about Windows 10 Creators Update is that the open command window here option in your context menu has been replaced with Powershell. You can do a lot more with Powershell than from cmd.exe but there are many commands which do not immediately translate and you may not want to take a bash at new things.
You can follow the instructions here to restore the option to your context menus, as with most things Windows the feature has not been lost but only hidden. It does involve rooting around in the registry please do back up before trying either of the methods here at Winareo. You will have your beloved cmd back and also retain the Powershell option in case you are feeling adventurous.
"Starting with Windows 10 build 14986, Microsoft enabled PowerShell by default in the context menu in File Explorer. The good old command "Open command window here" was removed. You can get the command prompt back in the context menu of File Explorer in Windows 10 Creators Update with a simple Registry tweak."
Here is some more Tech News from around the web:
- Project Scorpio shuns Ryzen in favour of 'evolved' AMD Jaguar CPU @ The Inquirer
- Android Devices Can Be Fatally Hacked By Malicious Wi-Fi Networks @ Slashdot
- McAfee is McAfee again, promises security with kum ba yah @ The Register
- Your chance to become a supercomputer superuser – for free @ The Register
- Apple’s $329 iPad is for people who have never upgraded their tablet @ Ars Technica
- Microsoft goes softly, softly on Windows 10 Creators Update privacy @ The Inquirer
Subject: Editorial | April 6, 2017 - 12:57 AM | Alex Lustenberg
Tagged: Z270E, windows 10, relive, podcast, pascal, NVIDA, Mad Catz, Imagination Technologies, ddr5, asus, amd
PC Perspective Podcast #444 - 04/6/17
Join us for an ASUS Z270 Motherboard, NVIDIA Quadro, AMD ReLive, DDR5 and more!
The URL for the podcast is: http://pcper.com/podcast - Share with your friends!
- iTunes - Subscribe to the podcast directly through the iTunes Store (audio only)
- Google Play - Subscribe to our audio podcast directly through Google Play!
- RSS - Subscribe through your regular RSS reader (audio only)
- MP3 - Direct download link to the MP3 file
Hosts: Jeremy Hellstrom, Josh Walrath, Allyn Malventano, Ken Addison
Subject: General Tech | April 5, 2017 - 10:23 PM | Scott Michaud
Tagged: windows 10, microsoft
A few days ago, we mentioned that early adopters of the Windows 10 Creators Update can access the new build early by running an opt-in tool from Microsoft. At the time, it was unclear whether users couple perform a clean install without downloading the Insider build, which would also require enrolling in the Insider program.
As it turns out, Microsoft, today, has updated their Media Creation tool to produce media for the Creators Update. I haven’t yet installed it, because performing a clean installation on your only PC takes a fairly clear schedule, but I’ll probably give my first impressions on this post tonight or tomorrow. I have already opened the ISO, though, and a lot of the files are dated March 18th, so I'm confident in the reports that this has been updated to Creators Update.
Again, I would recommend that the vast majority of users wait until at least April 11th, if not longer, to give Microsoft extra time for tuning the new build. The first couple of months of a new build have, thus far, involved frequent updates and some compatibility issues. Microsoft is confident with enthusiasts grabbing the bits tonight, so go ahead if you like, but it might be a little bumpy for weeks and/or months.
Subject: General Tech | March 31, 2017 - 08:53 PM | Scott Michaud
Tagged: windows 10, microsoft, creators update
- Windows Update will begin pushing the Creators Update on April 11th
- Early adopters can, this time, use a tool to force the update as early as April 5th.
- ISOs are currently available, but marked as Insider Preview.
- The earlier you update, the more patching you should expect to do, historically.
While Jeremy has already given a brief mention to the news that the Windows 10 Creators Update will begin rolling out on April 11th, Microsoft has just announced that users can opt-in as early as April 5th. If the Anniversary Update is any indication, then the average user should wait until Windows Update devices to passes them the new bits (or longer). In fact, the main reason (besides just liking new things) for forcing an early install should be “it was a convenient time”.
Of course, as I say this, I’m remembering my experience with the November 2015 update, refreshing Windows Update for two days. I was participating in an Epic Games game jam at the time, and I didn’t want the update to drop right in the middle of my work. It should be any minute now, right? ... Yes, Microsoft giving enthusiasts an explicit opt-in tool is a great step forward. I’m definitely glad they did it. I’m just emphasizing the point that the first few weeks of a Windows feature update are, historically, a bit dicey.
The ISOs for the final build (15063) are already out, but they’re currently on the Windows Insider Program website. I’m not sure if the contents will change at some point, and, if so, when that new ISO will be available for public consumption, so clean installers will probably want to wait a little bit still.
If previous updates are any indication, we’ll be in for about a month or two of updates every week or so until it gradually slows down to “Patch Tuesday”. Or, you can stay on Anniversary Edition (or another OS entirely). Personally, I’ll probably be installing the Creators Update sometime late next week.
Subject: General Tech | March 29, 2017 - 01:35 PM | Jeremy Hellstrom
Tagged: windows 10
Ars Technica takes you on a walk through the upcoming Creators Update for Windows 10, which will start being installed on machines in just under two weeks. Starting with the good, there are some interesting new features, such as Edge now being able to display EPUB titles natively even if you will not have the ability to mark up those pages as you can websites. It also sees the inclusion of Windows Holographic API, though as of yet nothing apart from MSPaint seems to benefit from this addition. Game Mode will also appear for users, with support for both win32 and UWP applications, though you will have to adjust settings in the non-UWP to enable the new feature.
There is a long list of other changes, for both better and worse, which you can check out in the full article.
"The next big update to Windows 10 is nearly upon us: Windows 10 version 1703, known as the Creators Update, will be published to Windows Update next Patch Tuesday, on April 11th."
Here is some more Tech News from around the web:
- Swan: Better Linux on Windows @ Hack a Day
- Source Parts on TaoBao: An Insider’s Guide @ Hack a Day
- Apple squashes cert-handling bug affecting macOS and iOS @ The Register
- So my ISP can now sell my browsing history – what can I do? @ The Register
Subject: Graphics Cards | March 21, 2017 - 07:47 PM | Scott Michaud
Tagged: windows 10, vulkan, sli, multi-gpu, crossfire
Update (March 22nd @ 3:50pm EDT): And the Khronos Group has just responded to my follow-up questions. LDA has existed since Windows Vista, at the time for assisting with SLI and Crossfire support. Its implementation has changed in Windows 10, but that's not really relevant for Vulkan's multi-GPU support. To prove this, they showed LDA referenced in a Windows 8.1 MSDN post.
Vulkan's multi-GPU extensions can be used on Windows 7 and Windows 8.x. The exact process will vary from OS to OS, but the GPU vendor can implement these extensions if they choose, and LDA mode isn't exclusive to Windows 10.
Update (March 21st @ 11:55pm EDT): I came across a Microsoft Support page that discusses issues with LDA in Windows 7, so it seems like that functionality isn't limited to WDDM 2.0 and Windows 10. (Why have a support page otherwise?) Previously, I looked up an MSDN article that had it listed as a WDDM 2.0 feature, so I figured DSOGaming's assertion that it was introduced with WDDM 2.0 was correct.
As such, LDA might not require a GPU vendor's implementation at all. It'll probably be more clear when the Khronos Group responds to my earlier request, though.
That said, we're arguing over how much a GPU vendor needs to implement; either way, it will be possible to use the multi-GPU extensions in Windows 7 and Windows 8.x if the driver supports it.
Update (March 21st @ 7:30pm EDT): The Khronos Group has just released their statement. It's still a bit unclear, and I've submit another request for clarification.
Specifically, the third statement:
If an implementation on Windows does decide to use LDA mode, it is NOT tied to Windows 10. LDA mode has been available on many versions of Windows, including Windows 7 and 8.X.
... doesn't elaborate what is required for LDA mode on Windows outside of 10. (It could be Microsoft-supported, vendor-supported, or something else entirely.) I'll update again when that information is available. For now, it seems like the table, below, should actually look something like this:
|macOS||Apple doesn't allow the Vulkan API to ship in graphics drivers.
|Linux / etc.||✓||✓||✓|
... but we will update, again, should this be inaccurate.
Update (March 20th @ 3:50pm EDT): The Khronos Group has just responded that the other posts are incorrect. They haven't yet confirmed whether this post (which separates "device groups" from the more general "multi-GPU in Vulkan") is correct, though, because they're preparing an official statement. We'll update when we have more info.
Original Post Below (March 19th @ 9:36pm EDT)
A couple of days ago, some sites have noticed a bullet point that claims Windows-based GPU drivers will need WDDM in “linked display adapter” mode for “Native multi-GPU support for NVIDIA SLI and AMD Crossfire platforms” on Vulkan. This note came from an official slide deck by the Khronos Group, which was published during the recent Game Developers Conference, GDC 2017. The concern is that “linked display adapter” mode is a part of WDDM 2.0, which is exclusive to Windows 10.
This is being interpreted as “Vulkan does not support multi-GPU under Windows 7 or 8.x”.
I reached out to the Khronos Group for clarification, but I’m fairly sure I know what this does (and doesn’t) mean. Rather than starting with a written out explanation in prose, I will summarize it into a table, below, outlining what is possible on each platform. I will then elaborate below that.
|macOS||Apple doesn't allow the Vulkan API to ship in graphics drivers.
|Linux / etc.||✓||✓||✓|
So the good news is that it’s possible for a game developer to support multi-GPU (through what DirectX 12 would call MDA) on Windows 7 and Windows 8.x; the bad news is that no-one might bother with the heavy lifting. Linked display adapters allow the developer to assume that all GPUs are roughly the same performance, have the same amount of usable memory, and can be accessed through a single driver interface. On top of these assumptions, device groups also hide some annoying and tedious work inside the graphics driver, like producing a texture on one graphics card and quickly giving it to another GPU for rendering.
Basically, if the developer will go through the trouble of supporting AMD + NVIDIA or discrete GPU + integrated GPU systems, then they can support Windows 7 / 8.x in multi-GPU as well. Otherwise? Your extra GPUs will be sitting out unless you switch to DirectX 11 or OpenGL (or you use it for video encoding or something else outside the game).
On the other hand, this limitation might pressure some developers to support unlinked multi-GPU configurations. There are some interesting possibilities, including post-processing, GPGPU tasks like AI visibility and physics, and so forth, which might be ignored in titles whose developers were seduced by the simplicity of device groups. On the whole, device groups was apparently a high-priority request by game developers, and its inclusion will lead to more multi-GPU content. Developers who can justify doing it themselves, though, now have another reason to bother re-inventing a few wheels.
Or... you could just use Linux. That works, too.
Again, we are still waiting on the Khronos Group to confirm this story. See the latest update, above.
Subject: Processors | March 13, 2017 - 08:48 PM | Sebastian Peak
Tagged: Windows 7, windows 10, thread scheduling, SMT, ryzen, Robert Hallock, processor, cpu, amd
AMD's Robert Hallock (previously the Head of Global Technical Marketing for AMD and now working full time on the CPU side of things) has posted a comprehensive Ryzen update, covering AMD's official stance on Windows 10 thread scheduling, the performance implications of SMT, Windows power management settings, and more. The post in its entirety is reproduced below, and also available from AMD by following this link.
It’s been about two weeks since we launched the new AMD Ryzen™ processor, and I’m just thrilled to see all the excitement and chatter surrounding our new chip. Seems like not a day goes by when I’m not being tweeted by someone doing a new build, often for the first time in many years. Reports from media and users have also been good:
- “This CPU gives you something that we needed for a long time, which is a CPU that gives you a well-rounded experience.” –JayzTwoCents
- Competitive performance at 1080p, with Tech Spot saying the “affordable Ryzen 7 1700” is an “awesome option” and a “safer bet long term.”
- ExtremeTech showed strong performance for high-end GPUs like the GeForce GTX 1080 Ti, especially for gamers that understand how much value AMD Ryzen™ brings to the table
- Many users are noting that the 8-core design of AMD Ryzen™ 7 processors enables “noticeably SMOOTHER” performance compared to their old platforms.
While these findings have been great to read, we are just getting started! The AMD Ryzen™ processor and AM4 Platform both have room to grow, and we wanted to take a few minutes to address some of the questions and comments being discussed across the web.
We have investigated reports alleging incorrect thread scheduling on the AMD Ryzen™ processor. Based on our findings, AMD believes that the Windows® 10 thread scheduler is operating properly for “Zen,” and we do not presently believe there is an issue with the scheduler adversely utilizing the logical and physical configurations of the architecture.
As an extension of this investigation, we have also reviewed topology logs generated by the Sysinternals Coreinfo utility. We have determined that an outdated version of the application was responsible for originating the incorrect topology data that has been widely reported in the media. Coreinfo v3.31 (or later) will produce the correct results.
Finally, we have reviewed the limited available evidence concerning performance deltas between Windows® 7 and Windows® 10 on the AMD Ryzen™ CPU. We do not believe there is an issue with scheduling differences between the two versions of Windows. Any differences in performance can be more likely attributed to software architecture differences between these OSes.
Going forward, our analysis highlights that there are many applications that already make good use of the cores and threads in Ryzen, and there are other applications that can better utilize the topology and capabilities of our new CPU with some targeted optimizations. These opportunities are already being actively worked via the AMD Ryzen™ dev kit program that has sampled 300+ systems worldwide.
Above all, we would like to thank the community for their efforts to understand the Ryzen processor and reporting their findings. The software/hardware relationship is a complex one, with additional layers of nuance when preexisting software is exposed to an all-new architecture. We are already finding many small changes that can improve the Ryzen performance in certain applications, and we are optimistic that these will result in beneficial optimizations for current and future applications.
The primary temperature reporting sensor of the AMD Ryzen™ processor is a sensor called “T Control,” or tCTL for short. The tCTL sensor is derived from the junction (Tj) temperature—the interface point between the die and heatspreader—but it may be offset on certain CPU models so that all models on the AM4 Platform have the same maximum tCTL value. This approach ensures that all AMD Ryzen™ processors have a consistent fan policy.
Specifically, the AMD Ryzen™ 7 1700X and 1800X carry a +20°C offset between the tCTL° (reported) temperature and the actual Tj° temperature. In the short term, users of the AMD Ryzen™ 1700X and 1800X can simply subtract 20°C to determine the true junction temperature of their processor. No arithmetic is required for the Ryzen 7 1700. Long term, we expect temperature monitoring software to better understand our tCTL offsets to report the junction temperature automatically.
The table below serves as an example of how the tCTL sensor can be interpreted in a hypothetical scenario where a Ryzen processor is operating at 38°C.
Users may have heard that AMD recommends the High Performance power plan within Windows® 10 for the best performance on Ryzen, and indeed we do. We recommend this plan for two key reasons:
- Core Parking OFF: Idle CPU cores are instantaneously available for thread scheduling. In contrast, the Balanced plan aggressively places idle CPU cores into low power states. This can cause additional latency when un-parking cores to accommodate varying loads.
- Fast frequency change: The AMD Ryzen™ processor can alter its voltage and frequency states in the 1ms intervals natively supported by the “Zen” architecture. In contrast, the Balanced plan may take longer for voltage and frequency (V/f) changes due to software participation in power state changes.
In the near term, we recommend that games and other high-performance applications are complemented by the High Performance plan. By the first week of April, AMD intends to provide an update for AMD Ryzen™ processors that optimizes the power policy parameters of the Balanced plan to favor performance more consistent with the typical usage models of a desktop PC.
Simultaneous Multi-threading (SMT)
Finally, we have investigated reports of instances where SMT is producing reduced performance in a handful of games. Based on our characterization of game workloads, it is our expectation that gaming applications should generally see a neutral/positive benefit from SMT. We see this neutral/positive behavior in a wide range of titles, including: Arma® 3, Battlefield™ 1, Mafia™ III, Watch Dogs™ 2, Sid Meier’s Civilization® VI, For Honor™, Hitman™, Mirror’s Edge™ Catalyst and The Division™. Independent 3rd-party analyses have corroborated these findings.
For the remaining outliers, AMD again sees multiple opportunities within the codebases of specific applications to improve how this software addresses the “Zen” architecture. We have already identified some simple changes that can improve a game’s understanding of the "Zen" core/cache topology, and we intend to provide a status update to the community when they are ready.
Overall, we are thrilled with the outpouring of support we’ve seen from AMD fans new and old. We love seeing your new builds, your benchmarks, your excitement, and your deep dives into the nuts and bolts of Ryzen. You are helping us make Ryzen™ even better by the day. You should expect to hear from us regularly through this blog to answer new questions and give you updates on new improvements in the Ryzen ecosystem.
Such topics as Windows 7 vs. Windows 10 performance, SMT impact, and thread scheduling will no doubt still be debated, and AMD has correctly pointed out that optimization for this brand new architecture will only improve Ryzen performance going forward. Our own findings as to Ryzen and the Windows 10 thread scheduler appear to be validated as AMD officially dismisses performance impact in that area, though there is still room for improvement in other areas from our initial gaming performance findings. As mentioned in the post, AMD will have an update for Windows power plan optimization by the first week of April, and the company has "already identified some simple changes that can improve a game’s understanding of the 'Zen' core/cache topology, and we intend to provide a status update to the community when they are ready", as well.
It is refreshing to see a company publicly acknowledging the topics that have resulted in so much discussion in the past couple of weeks, and their transparency is commendable, with every issue (that this author is aware of) being touched on in the post.
** UPDATE 3/13 5 PM **
AMD has posted a follow-up statement that officially clears up much of the conjecture this article was attempting to clarify. Relevant points from their post that relate to this article as well as many of the requests for additional testing we have seen since its posting (emphasis mine):
"We have investigated reports alleging incorrect thread scheduling on the AMD Ryzen™ processor. Based on our findings, AMD believes that the Windows® 10 thread scheduler is operating properly for “Zen,” and we do not presently believe there is an issue with the scheduler adversely utilizing the logical and physical configurations of the architecture."
"Finally, we have reviewed the limited available evidence concerning performance deltas between Windows® 7 and Windows® 10 on the AMD Ryzen™ CPU. We do not believe there is an issue with scheduling differences between the two versions of Windows. Any differences in performance can be more likely attributed to software architecture differences between these OSes."
So there you have it, straight from the horse's mouth. AMD does not believe the problem lies within the Windows thread scheduler. SMT performance in gaming workloads was also addressed:
"Finally, we have investigated reports of instances where SMT is producing reduced performance in a handful of games. Based on our characterization of game workloads, it is our expectation that gaming applications should generally see a neutral/positive benefit from SMT. We see this neutral/positive behavior in a wide range of titles, including: Arma® 3, Battlefield™ 1, Mafia™ III, Watch Dogs™ 2, Sid Meier’s Civilization® VI, For Honor™, Hitman™, Mirror’s Edge™ Catalyst and The Division™. Independent 3rd-party analyses have corroborated these findings.
For the remaining outliers, AMD again sees multiple opportunities within the codebases of specific applications to improve how this software addresses the “Zen” architecture. We have already identified some simple changes that can improve a game’s understanding of the "Zen" core/cache topology, and we intend to provide a status update to the community when they are ready."
We are still digging into the observed differences of toggling SMT compared with disabling the second CCX, but it is good to see AMD issue a clarifying statement here for all of those out there observing and reporting on SMT-related performance deltas.
** END UPDATE **
Editor's Note: The testing you see here was a response to many days of comments and questions to our team on how and why AMD Ryzen processors are seeing performance gaps in 1080p gaming (and other scenarios) in comparison to Intel Core processors. Several outlets have posted that the culprit is the Windows 10 scheduler and its inability to properly allocate work across the logical vs. physical cores of the Zen architecture. As it turns out, we can prove that isn't the case at all. -Ryan Shrout
Initial reviews of AMD’s Ryzen CPU revealed a few inefficiencies in some situations particularly in gaming workloads running at the more common resolutions like 1080p, where the CPU comprises more of a bottleneck when coupled with modern GPUs. Lots of folks have theorized about what could possibly be causing these issues, and most recent attention appears to have been directed at the Windows 10 scheduler and its supposed inability to properly place threads on the Ryzen cores for the most efficient processing.
I typically have Task Manager open while running storage tests (they are boring to watch otherwise), and I naturally had it open during Ryzen platform storage testing. I’m accustomed to how the IO workers are distributed across reported threads, and in the case of SMT capable CPUs, distributed across cores. There is a clear difference when viewing our custom storage workloads with SMT on vs. off, and it was dead obvious to me that core loading was working as expected while I was testing Ryzen. I went back and pulled the actual thread/core loading data from my testing results to confirm:
The Windows scheduler has a habit of bouncing processes across available processor threads. This naturally happens as other processes share time with a particular core, with the heavier process not necessarily switching back to the same core. As you can see above, the single IO handler thread was spread across the first four cores during its run, but the Windows scheduler was always hitting just one of the two available SMT threads on any single core at one time.
My testing for Ryan’s Ryzen review consisted of only single threaded workloads, but we can make things a bit clearer by loading down half of the CPU while toggling SMT off. We do this by increasing the worker count (4) to be half of the available threads on the Ryzen processor, which is 8 with SMT disabled in the motherboard BIOS.
SMT OFF, 8 cores, 4 workers
With SMT off, the scheduler is clearly not giving priority to any particular core and the work is spread throughout the physical cores in a fairly even fashion.
Now let’s try with SMT turned back on and doubling the number of IO workers to 8 to keep the CPU half loaded:
SMT ON, 16 (logical) cores, 8 workers
With SMT on, we see a very different result. The scheduler is clearly loading only one thread per core. This could only be possible if Windows was aware of the 2-way SMT (two threads per core) configuration of the Ryzen processor. Do note that sometimes the workload will toggle around every few seconds, but the total loading on each physical core will still remain at ~%50. I chose a workload that saturated its thread just enough for Windows to not shift it around as it ran, making the above result even clearer.
Synthetic Testing Procedure
While the storage testing methods above provide a real-world example of the Windows 10 scheduler working as expected, we do have another workload that can help demonstrate core balancing with Intel Core and AMD Ryzen processors. A quick and simple custom-built C++ application can be used to generate generic worker threads and monitor for core collisions and resolutions.
This test app has a very straight forward workflow. Every few seconds it generates a new thread, capping at N/2 threads total, where N is equal to the reported number of logical cores. If the OS scheduler is working as expected, it should load 8 threads across 8 physical cores, though the division between the specific logical core per physical core will be based on very minute parameters and conditions going on in the OS background.
By monitoring the APIC_ID through the CPUID instruction, the first application thread monitors all threads and detects and reports on collisions - when a thread from our app is running on the same core as another thread from our app. That thread also reports when those collisions have been cleared. In an ideal and expected environment where Windows 10 knows the boundaries of physical and logical cores, you should never see more than one thread of a core loaded at the same time.
Click to Enlarge
This screenshot shows our app working on the left and the Windows Task Manager on the right with logical cores labeled. While it may look like all logical cores are being utilized at the same time, in fact they are not. At any given point, only LCore 0 or LCore 1 are actively processing a thread. Need proof? Check out the modified view of the task manager where I copy the graph of LCore 1/5/9/13 over the graph of LCore 0/4/8/12 with inverted colors to aid viewability.
If you look closely, by overlapping the graphs in this way, you can see that the threads migrate from LCore 0 to LCore 1, LCore 4 to LCore 5, and so on. The graphs intersect and fill in to consume ~100% of the physical core. This pattern is repeated for the other 8 logical cores on the right two columns as well.
Running the same application on a Core i7-5960X Haswell-E 8-core processor shows a very similar behavior.
Click to Enlarge
Each pair of logical cores shares a single thread and when thread transitions occur away from LCore N, they migrate perfectly to LCore N+1. It does appear that in this scenario the Intel system is showing a more stable threaded distribution than the Ryzen system. While that may in fact incur some performance advantage for the 5960X configuration, the penalty for intra-core thread migration is expected to be very minute.
The fact that Windows 10 is balancing the 8 thread load specifically between matching logical core pairs indicates that the operating system is perfectly aware of the processor topology and is selecting distinct cores first to complete the work.
Information from this custom application, along with the storage performance tool example above, clearly show that Windows 10 is attempting to balance work on Ryzen between cores in the same manner that we have experienced with Intel and its HyperThreaded processors for many years.
Subject: General Tech | March 3, 2017 - 01:33 PM | Jeremy Hellstrom
Tagged: microsoft, windows 10
If you are using Windows 10 Pro or Enterprise, you may have already disabled the automatic reboot function after updates are installed but for Home users after the Anniversary update, that has not been possible. It turns out there are a lot of users quite upset with unplanned reboots, especially those who leave their computers running overnight or while they are away. Microsoft have accepted this feedback and will return the ability to delay reboots to owners of the Home Edition in their next update. In the meantime, The Register describes a way in which you can regain a little more control over automatic reboots with your current build.
"Since the Windows 10 Anniversary Update in 2016, there is no way to prevent Windows 10 [Home] from automatically installing updates and rebooting your PC," fumed one vulture fan, John, who added that a group policy can be set on W10 Pro and Enterprise editions to prevent automated restarts."
Here is some more Tech News from around the web:
- Skype-on-Linux graduates from Alpha to Beta status @ The Register
- Google's troll-destroying AI can't cope with typos @ The Register
- biquiti UniFi AP AC HD WiFi Access Point (UAP-AC-HD) @ Custom PC Review
- Windows Phone users may find it harder to find love @ The Inquirer
Subject: General Tech | February 17, 2017 - 07:01 AM | Scott Michaud
Tagged: windows 10, microsoft
Don’t worry if you didn’t receive cumulative Windows Updates this month.
At first, Microsoft showed no love for Valentine’s Day when they delayed the update that was supposed to roll out to the public. No explanation was provided. Two days later, Microsoft decided to write off the whole month. Everything that has been fixed since January 10th will be delayed until March 14th.
This is quite the wait. Peter Bright of Ars Technica notes that “off-cycle updates are also unpopular”. Yes, IT professionals hate it when software vendors are difficult to schedule around. I’m not sure how much that had to do with this decision, though. On the one hand, when a new build launches to the public, it’s not uncommon to have an update (or more) per week over the first couple of months. On the other hand, it would be reasonable for Microsoft to assume that customers, those who carefully test patches before deploying them, would not have ingested a huge, nebulous feature release into their network just weeks after launch. Still, out-of-band updates happen, and it’s interesting that it didn’t happen in this circumstance.
One thing that this patch should have fixed, however, is delayed or clipped display output in games (and other 3D applications) on multi-monitor systems. While not as critical as security, it is probably annoying for anyone affected to need to wait another 28 days. Microsoft claims it will be fixed then, though.