2

I dont think you can uninstall it. In this situation, i would complete the patching process. Run the config wizard on all server and complete the patch. I would also do the same on the lower environment as well because your prod is now (may be) higher build number.


2

Couple of things to make sure before any conclusion: make sure you ran config wizard on all SharePoint servers after patching. from add/remove program, Make sure Jan 2019 Kb patches listed there (kb4461605) also from central admin > upgrade & migration > check product and patch installation status on this page, make sure Jan 2019 KB number is ...


2

Both of the CU (Dec 2018 & Nov 2018) are pretty much solid as i have not seen any issue regarding this. It is safe to install one of these. Before installing these CU make sure couple of things. You farm should be SP1 Level before installing these CUs. If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post....


1

Users will need: member of the farm administrators group local admin on SharePoint server Security Admin and DBCreator role on SQL db_owner on all existing SharePoint databases This blog post lays out additional details and recommendations, including a recommendation to grant these permissions to a group rather than individual users, so that you can add/...


1

Updates are displayed here: https://docs.microsoft.com/de-de/officeupdates/sharepoint-updates The currently latest CU is KB 4464514 - April 2019 The problem you mentioned was not due to a SharePoint update but rather .net-Framework.


1

It is recommended to always be on the CU which is 1 month prior to the current month. That way you are on the most stable CU and aware of any issues or exceptions occurring due to the current month CU . I have recently patched my SharePoint 2013 environment with the April 2019 patch and it looks the most stable patch right now . Following is the ...


1

both KB articles you mentioned are the security updates, in the description page, it mentioned it replace the old security updates. But I would rather compare with SharePoint December CU (KB4461555) vs August CU (KB4032247) . If you go throug each cu, you will notice it include that months Security updates as well as previous. I highly recommend install ...


1

You only need to apply the latest non-language and language dependent fixes. Since March did not have a language-dependent fix, you will need to apply the Feb 2019 language-dependent fix. https://support.microsoft.com/en-us/help/4462170/february-12-2019-update-for-sharepoint-server-2019-language-pack-kb446 https://support.microsoft.com/en-us/help/4462199/...


1

It seems that this is an ongoing "bug" with IE updates as there is a workaround mentioned the following two KB articles for IE Security Updates: Cumulative security update for Internet Explorer: March 12, 2019 Cumulative security update for Internet Explorer: April 9, 2019


1

I have done a test in my SharePoint 2013, patched on SharePoint servers with Jan 2019 CU on SP 2013 Servers. After patching, the SharePoint build number is equivalent to Dec 2018 CU instead of Jan 2019 CU. It is a normal behavior.


1

The best source for this question is Todd Klindt's fantastic SharePoint 2013 Build Numbers page. You can find a column Bugs, Notes and regressions for every patch. Your noted patches do not have any specific drawback, except the .NET Security Patch issue. But this is not a SharePoint-CU specific issue, it was caused by a Windows .NET Security Patch. This ...


1

"The only component directly accessing the configuration database is the SharePoint foundation component" But as you know their is no SharePoint foundation patch released in the October 2018 for SharePoint Server 2010. So in this case configuration database version will not change and remain same. Read the below article, which explain int he detail. Common ...


Only top voted, non community-wiki answers of a minimum length are eligible