win10 support end date isUntil now everything is going as normal, updating and everything.
Windows 10 will end suport to shortly.
October 14, 2025
win10 support end date isUntil now everything is going as normal, updating and everything.
Windows 10 will end suport to shortly.
rem PacketCoalescingFilter enabled for pure throughput when lower CPU utilization is important.
powershell.exe Set-NetOffloadGlobalSetting -PacketCoalescingFilter enabled >nul
rem Receive Segment Coalescing (RSC Enable for slightly higher throughput when lower CPU utilization is important.
netsh int tcp set global rsc=enabled >nul
rem Disable TCP selective acks option for better CPU utilization
powershell.exe new-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters -Name SackOpts -PropertyType dword -Value 0 -force >nul
rem This NDIS 5 setting allows for reducing CPU load by offloading some tasks required to maintain the TCP/IP stack to the network card.
powershell.exe New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters -Name DisableTaskOffload -PropertyType dword -Value 0 -force >nul
rem start with CPU1 for RSS (Receive Side Scaling Base set to value of 1) to let CPU0 do other important things.
powershell.exe New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\services\NDIS\Parameters -Name RssBaseCpu -PropertyType dword -Value 1 -force >nul
rem Set the maximum number of RSS CPUs with the MaxNumRssCpus. DUO CORE set value of 2.
powershell.exe New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\services\NDIS\Parameters -Name MaxNumRssCpus -PropertyType dword -Value 2 -force >nul
rem System Responsiveness determines the percentage of CPU resources that should be guaranteed to low-priority tasks.
powershell.exe New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile' -Name SystemResponsiveness -PropertyType dword -Value 0 -force >nul
rem Set an RSS profile for a NUMA server without dynamic load balancing, Base Processor Number 1, Max Processor Number 2,Max Processors 2
powershell.exe (Set-NetAdapterRss -Name * -Profile NUMAStatic -BaseProcessorNumber 2 -MaxProcessorNumber 2 -MaxProcessors 2) >nul
rem Because the removal of node splitting can potentially impact existing applications, a registry value is available to allow
rem opting back into the legacy node splitting behavior. Node splitting can be re-enabled by creating a REG_DWORD value
rem named "SplitLargeNodes" with value 1 underneath.
powershell.exe New-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\NUMA' -Name 'SplitLargeNodes' -PropertyType dword -Value 1 -force >nul
So...I wouldn't do that, sooner or later you will stop receiving updates through the official Microsoft channel
Why wouldn't he? That's exactly the point of this forum and I love it! I haven't even looked for a TPM workaround (my CPU supports it) and I've encountered one anyway. Awesome! Excellent work. Looking forward to the progress here. Even if updates would get disabled (unlikely, as that would compromise security even further) it doesn't mean there won't be another workaround.I wouldn't do that, sooner or later you will stop receiving updates through the official Microsoft channel
Better to think what we will do!We'll see what Microsoft does with unsupported machines in the near future