November 2025 CU for SharePoint Server Subscription Edition is available for download

12 Comments

1. 

   Karthikeyan Parasuraman
   On 12. November 2025 Permalink

   Hi Stefan,
   As per below blog, there are still few issues need to be addressed for SPSE version. When can we expect that to be addressed ?

   https://blog.stefan-gossner.com/2025/09/25/summary-and-status-of-issues-identified-with-september-2025-cu-for-sharepoint/

   Reply
   1. 

      Stefan Goßner
      On 12. November 2025 Permalink

      Hi Karthikeyan,
      great question – the remaining issues are currently under investigation.
      No ETA available but I would expect for all to be resolved > 4 months.
      Cheers,
      Stefan

      Reply
2. 

   Mike
   On 14. November 2025 Permalink

   I cannot get SharePoint Administration service to start during the PS Config – no matter what account it is set to at “Log On As”

   11/14/2025 12:00:13 20 ERR An exception of type System.InvalidOperationException was thrown. Additional exception information: Cannot start service SPAdminV4 on computer ‘.’.
   System.InvalidOperationException: Cannot start service SPAdminV4 on computer ‘.’. —> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
   — End of inner exception stack trace —
   at System.ServiceProcess.ServiceController.Start(String[] args)
   at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
   at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
   at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
   at Microsoft.SharePoint.Administration.SPServerRoleManager.<>c__DisplayClass19_0.b__0()
   at Microsoft.SharePoint.Administration.SPServerRoleManager.ConfigureServiceInstance(SPServiceInstance serviceInstance)
   at Microsoft.SharePoint.Administration.SPServerRoleManager.ConfigureServer(Boolean throwOnFailure)
   at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)
   at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

   I have added the Registry setting for ServicesPipeTimeout based on some other information I found, but nothing will start this service

   Reply
   1. 

      Stefan Goßner
      On 14. November 2025 Permalink

      Hi Mike,
      please check this article:
      https://blog.stefan-gossner.com/2025/09/16/trending-issue-sptimerv4-fails-to-start-on-windows-server-2025-after-installing-september-2025-cu/
      Cheers,
      Stefan

      Reply
      1. 

         Mike
         On 14. November 2025 Permalink

         Thanks Stefan – this was a huge help! I have been fighting with this all day – all I can say is Lifesaver!

         Reply
         1. 

            Stefan Goßner
            On 14. November 2025 Permalink

            😊

            Reply
3. 

   Salil
   On 25. November 2025 Permalink

   Any Idea about the issue, we started getting after installing November 2025 CU. This cause the app pool to stop automatically.
   EVENT ID: 1000

   Faulting application name: w3wp.exe, version: 10.0.20348.1, time stamp: 0x405e4c14
   Faulting module name: KERNELBASE.dll, version: 10.0.20348.4294, time stamp: 0x73e9e45d
   Exception code: 0xe0434352
   Fault offset: 0x000000000003f33c
   Faulting process id: 0x159c
   Faulting application start time: 0x01dc5e0ffb866a91
   Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
   Faulting module path: C:\Windows\System32\KERNELBASE.dll
   Report Id: a422c282-a8b4-4490-92c8-6e5b3bb10e11
   Faulting package full name:
   Faulting package-relative application ID:

   EVENT ID 1325:
   An unhandled exception occurred and the process was terminated.

   Application ID: /LM/W3SVC/XXXXXXXXXX/ROOT

   Process ID: XXXXX

   Exception: System.Runtime.InteropServices.SEHException

   Message: External component has thrown an exception.

   StackTrace: at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

   Reply
   1. 

      Stefan Goßner
      On 25. November 2025 Permalink

      Hi Salil,
      this is an error raised in unmanaged code and returned to managed code generating this System.Runtime.InteropServices.SEHException:
      https://learn.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.sehexception?view=net-10.0
      From the callstack this could be an exception raised by a problem in your AV solution during AMSI Scan operations.
      Cheers,
      Stefan

      Reply
      1. 

         Salil
         On 26. November 2025 Permalink

         Thanks for your response! We got to know from MS Support that this is an issue with Nov 2025 CU.

         Reply
         1. 

            Tomas
            On 6. December 2025 Permalink

            Any workaround for this issue other than to disable your AV/AMSI ?

            Reply
         2. 

            Johan
            On 10. December 2025 Permalink

            Hi,
            I have the same problem after installing the November CU update.
            Do you have a already a workaround for this? We have two application pools that keep crashing under high load since the update.

            Thanks,

            Johan

            Reply
4. 

   Chris
   On 9. December 2025 Permalink

   Hi,

   We recently migrated from SharePoint 2016 to Server Subscription Edition but there seems to be so many security fix errors that it’s difficult to differentiate between post-migration issues and outstanding issues relating to SharePoint security fixes.

   Due to the time it took to setup our DEV and Prod environments, we haven’t moved past August 2025 yet but I’m struggling to work out which patch is ‘safe’ to move to given the number of problems identified or still under investigation.

   Why are there so many issues to correct/mitigate on SSE?

   Thanks,

   Chris

   Reply