Microsoft yesterday released a bunch of updates for its different OS platforms, which solely included bug fixes and performance improvements and were devoid of any new features. The most significant update was for the Windows Server 2016 which fixes a really critical bug in the OS.
The Permission Vanishing Bug In Server 2016
“Addresses an issue in File Explorer that sometimes deletes the permissions of a shared parent folder when you delete the shared child folder”, the fix-log reads. As The Register reports, the bug was first spotted by a user in TechNet forum and it removed the permission of the parent folder when the child folder was deleted. Soon after, a Redditor experienced a similar issue and was able to consistently reproduce the bug as well. The Reddit post reads as follows:-
“On Server 2016, with a Shared folder that’s top level is set to “<security group> Read/Execute This folder only” and has a child folder that has inheritance enabled and has any explicitly defined permission, when the Child folder is deleted, the top level “<security group> Read/Execute This folder Only” will be REMOVED.
When we first ran into this, we thought it to be crazy. Permissions should NEVER flow up.
At this point, we have been able to reproduce this issue at-will on
Server 2016 file server failover cluster with up to March updates.
same as previous, with April updates.
Server 2016 NON-cluster with March updates.
We were NOT able to reproduce on Server 2012R2 or 2008R2.”
While there were workarounds to the bug, such as using the command line, removing the folder via UNC path or removing any explicitly defined permissions on child folders before deletion, there was no proper fix for the same until yesterday. KB4467684 addresses fixes this issue.
UPDATE: The flaw in the Windows Server 2016 permissions dialog functions library, that resulted in removal of parent folder permissions under certain conditions when deleting a child folder, has been fixed in a patch released today.https://t.co/aXrNIO8Pie
— SwiftOnSecurity (@SwiftOnSecurity) November 27, 2018
Cherry Picked Deployment
The Update for Windows 10, is exclusive only for Windows 10 Build 1709 and Windows 10 Build 1803 users, as of now, and is named as the KB4467681 and KB4467682. As far as Windows 10 Build 1703 is concerned, Microsoft ended support for them last month, but Enterprise and Education edition owners got the latest update. The lucky people (read that as unlucky) people who got the Build 1809 Update, aka the October 2018 Update, will have to wait a bit longer to get their update, since it’s currently available as a part of the Windows Insider Program (KB4469342).
Both KB4467681 and KB4467682 addresses a number of issues, but have a common issue associated with them as well, i.e, “After installing this update, users may not be able to use the Seek Bar in Windows Media Player when playing specific files.”, as Microsoft says in their blog. Notable fixes included a fix for the failure of reconnecting mapped devices on login and a bug that stopped users setting Win32 app defaults for certain file types.
iCloud Compatibility Issues Resolved
Microsoft, or rather Apple, finally addressed the incompatibility issues between iCloud and Windows 10 Build 1809. The fix-log reads: “Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or syncing Shared Albums after updating to Windows 10, version 1809“. Microsoft suggests that users should update “iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809”, to ensure that the compatibility issues are fixed.