Microsoft releases KB4464330 for Windows 10 version 1809 to fix the issue that resulted in the deletion of user profile when upgrading to the OS Version 1809. After the release of Windows 10 1809 (October update), many users reported a serious issue with this update. As the users started to install the latest update, they reported that the upgrade process is wiping out their data from user profile. This included documents, pictures, and personal files along with other installed programs. After the upgrade, the data was not found and this annoyed the Windows 10 users.
The statement from Microsoft:
“We have paused the rollout of the Windows 10 October 2018 Update (version 1809)* for all users as we investigate isolated reports of users missing some files after updating.”
After a week now, MS released an update for the issue. The updated will be delivered by your Update Management solution, like WSUS or Windows Updated for Business. For a manually download visit the MS Update catalog: catalog http://www.catalog.update.microsoft.com/Search.aspx?q=KB4464330%20
This KB addresses following changes:
- Addresses an issue where an incorrect timing calculation may prematurely delete user profiles on devices subject to the “Delete user profiles older than a specified number of day” group policy.
- Security updates to Windows Kernel, Microsoft Graphics Component, Microsoft Scripting Engine, Internet Explorer, Windows Storage and Filesystems, Windows Linux, Windows Wireless Networking, Windows MSXML, the Microsoft JET Database Engine, Windows Peripherals, Microsoft Edge, Windows Media Player, and Internet Explorer.
Microsoft releasd last week two new updates during the newly announced servicing model.
This updates, named”October, 2016 Security Only Quality Update for Windows Server 2012 R2 (KB3192392)” and “October, 2016 Security Monthly Quality Rollup for Windows Server 2012 R2 (KB3185331)” causing the System Center Operation Manager Console crashing when tying to use the Windows Computers view.
Currently there is no other way as removing the update from your management servers where the SCOM console is installed.
Let me know if you have a better solution!
The newest Version of System Center Configuration Manager Current Branch (1606) is rolling out these days with a lot of new features and opportunities.
As the update is rolled out globally in the coming weeks, it will be automatically downloaded and you will be notified when it is ready to install from the “Updates and Servicing” node in your Configuration Manager console. If you can’t wait to try these new features, this PowerShell script can be used to ensure that you are in the first wave of customers getting the update.
Beginning in Configuration Manager version 1606, you can use the Configuration Manager client setting to manage the Office 365 client agent. Configure your Client Settings \ Software Updates Settings. There you can find now a new option called “Enable management of the Office 365 Client Agent“.
After you configure this setting and deploy Office 365 updates, the Configuration Manager client agent communicates with the Office 365 client agent to download Office 365 updates from a distribution point and install them. Configuration Manager takes inventory of Office 365 ProPlus Client settings.
Find more details on TechNet: https://technet.microsoft.com/en-us/library/mt741983.aspx
In the past we used the guide from Kent Agerlund (MVP) for cleaning up the WSUS Database in ConfigMgr, also called the house of cards! This guide is still very popular and of course necessary for having a correct configured WSUS Server. As Kent mentioned, you should do the cleanup task every Monday morning before you start any other work :-)!
But now we got a new option in ConfigMgr 1511 when we setup the Software Update Point. This will allow ConfigMgr to cleanup the WSUS Database and remove any obsolet updates from the WSUS DB.
To enable and run the WSUS cleanup job
In the Configuration Manager console, navigate to Administration > Overview > Site Configuration > Sites.
Click Configure Site Components in the Settings group, and then click Software Update Point to open Software Update Point Component Properties.
Click the Supersedence Rules tab, select Run WSUS cleanup wizard, and then click OK.
Thanks to the MS Product Team to integrate this feature in future ConfigMgr versions!
Hi, I’m Alain Schneiter
This is my first post in this blog! I’m verry proud to be a part of this team.
Today we had the issue with a failing Tasksequence during the OSD of a Windows 2012 Server. The SMSts.log contained following error:
TS::Utility::GetTSMDataPath( sDataDir ), HRESULT=80070002
Failed to set log directory. Some execution history may be lost.
The system cannot find the file specified. (Error: 80070002; Source: Windows) Continue reading “SCCM 2012 – Task sequence fails in SCCM if software updates require multiple restarts”