As Microsoft releases a new Windows 10 beta, we get a patching break. Windows 8.1 in fact only has a Flash update to install. Meanwhile, Redmond has been busy with changes to the upcoming Creator’s release.
Upcoming Windows 10 changes
Dona Sarkar announced a beta release that makes quite a few changes to Windows update. As she noted on the blog site, the following changes are expected in the next large feature release expected around April of 2017:
A feature in the GUI to pause updates for 35 days. We’ve added an option that will enable you to pause updates on your computer for up to 35 days. While this feature already exists for Windows pro and above now, it’s only available via group policy or the registry. This capability will unfortunately only be available on Professional, Education, and Enterprise editions of Windows.
A feature to allow you to decide whether or not to include driver updates when you update Windows. Once again, this capability will be available on Professional, Education, and Enterprise editions of Windows.
A new icon to the Windows Update Settings page to make easier to see your update status at a glance.
Improvements to the logic to better detect if the PC’s display is actively being used for something, such as projecting, and avoid attempting to restart.
Windows Insiders with the Home edition of Windows will now also be able to leverage the increased 18 hour max window for Active Hours.
For those of you on the 1607 version of Windows 10, I’ll urge you to upvote my ask, that all customers of Microsoft, not just those who purchase Windows 10 professional sku’s and above to have the ability to pause updates. Consumers who are running Windows 10 current branch from July to November were rebooting about once a week. Given that folks have coded up tools to block Windows 10 updates, it showcases that all is not well with Windows updates.
What to do: Look for more changes to updating to come.
Office used in remote attacks
This month’s Office patches affect Word 2016 and showcase how Office can be used to take control of your computer. This vulnerability fixes an Office Memory Corruption Vulnerability
The following patches are included in this release:
3128057 – Word 2016 32bit
3141486 – SharePoint 2016
The following non security updates are included in the patch for SharePoint 2016:
Some terms are translated into multiple languages to make sure that the meaning is accurate.
You can’t access the Shortcuts link through the keyboard in grid edit mode of a SharePoint task list. In addition, screen readers can’t read or access information panels in SharePoint Server 2016.
The PSConfig tool may recommend incorrect cmdlets.
Sometimes, the PSConfig tool shows the upgrade as 100 percent completed even though it still takes some time before the tool moves to the next status. This problem occurs because the tool must complete some minor steps after it upgrades the products. Progress messages are displayed for these steps.
The patch fixes the following cmdlet legacy issues of the Administrative Actions Logging feature: Support partial execution for the cmdlet and update the help document correspondingly.
It refines the messages for some exceptions and logs.
After you try to configure and use the Lotus Notes connector for SharePoint Server, the crawl fails.
You can’t use the CSOM API to set the BookingType property for enterprise resources in projects.
A system access control list (SACL) isn’t read correctly for large file paths that exceed the Windows limitation of 260 characters. This causes the SACL to be discoverable by any user in the query results even if the user doesn’t have the appropriate permissions.
After you make multiple changes to the same user in quick succession in SharePoint Server 2016, the Quick Sync job can’t be completed successfully.
When you configure hybrid taxonomy, the specified Local Term Store Name parameter is now case-insensitive even though it was previously case-sensitive.
You can’t restore site collection that have site URLs. Additionally, you receive the following error message:
Error: Violation of PRIMARY KEY constraint ‘PK_SiteUrlMap’. Cannot insert duplicate key in object ‘dbo.SiteUrlMap’
When you add a subtask to an existing subtask of a SharePoint task list, multiple subtasks are created instead of just one in certain conditions.
When you copy and paste subtasks in grid edit mode of a SharePoint task list, multiple subtasks are created unexpectedly.
SharePoint Server 2016 becomes unresponsive and the server experiences high CPU usage that requires a restart. Additionally, you can’t access sites, or you get extremely slow page load times.
When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, you have an assignment that has 35 hours total work, and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
This article is part of our premium content. Join Now.
Trademarks: Microsoft and Windows are registered trademarks of Microsoft Corporation. The Windows Secrets series of books is published by Wiley Publishing Inc. The Windows Secrets Newsletter, WindowsSecrets.com, WinFind, Windows Gizmos, Security Baseline, Patch Watch, Perimeter Scan, Wacky Web Week, the Logo Design (W, S or road, and Star), and the slogan Everything Microsoft Forgot to Mention all are trademarks and service marks of iNET Interactive. All other marks are the trademarks or service marks of their respective owners.
to allow for analysis of how people use our website in order to
improve your experience and our services.
By continuing to use our website, you agree to the use of such cookies. Click here for more information on our