Windows 10: PreferredNode of a service not working anymore using WS2022

Hello,I was using the preferredNode attribute for services sc preferredNode <ServiceName> #Node in the past to set the initial Numa node memory and cpu affinity.Since I switched to Windows Server 2022 OS Build 20348.1249 the cpu affinity is not working anymore. The underlying executable is always pinned to Node 0.I double checked the behavior on a WS2019 instance, there it works fine, setting preferredNode to 1 starts the executable with cpu affinity at Node 1.Anyone facing the same problem and found a solution?ThanksMatthias

:)

 

Windows 10 Backup not working anymore since last update; Code 0x80070015

Hello,

We regret for the inconvenience caused to you. And I do appreciate your efforts and time.

I suggest you to follow the below steps to check the status of Volume Shadow Copy service and SPP services.

Note: You must be logged on as an administrator to perform these steps.

• Press the windows key + R to open the Run Command Utility. Type in
  services.msc and press Enter to open the Windows Services console.
• If the SPP service is disabled, double-click it to open the service properties.
• If Volume Shadow Copy service is disabled, double-click it to open
  
• the service properties
• Click the Startup type list, click
  Automatic (Delayed Start), and then click Apply.
• Under Service status, click Start.

Coming towards the Outlook issue as you mentioned "Outlook 2010 with iCoud Add in doesn't work anymore",
please be informed, there is a separate forum for office, I suggest you to post your query in Office forum.

Follow the below link to post query.

Redirecting

Let us know the status of the issue. We will assist you further.

 

Windows 10 infinite restart black screen


The tutorials provided are just a list of troubleshooting steps. Use only the steps which apply to you.

Since none of the troubleshooting steps here worked, I'd suggest you do a Clean install.

John

 

DriverPack just doesn't work anymore all of a sudden?

Nothing I can see aside from a failed service.

Have you confirmed on other PCs that the software acts the same as suggested above?

That might clarify if its your PC or their service for you...

Also fwir on Reddit and other places, folks seem to be ditching DriverPack for SDI as @Solaris17 suggests. You might consider following suit especially if DPs service is no longer consistent or running so long as you require the use of such a utility.