Forum Widgets
Latest Discussions
Connection Refused at TCP/IP Level
Guys, i have a web application running on Windows 2025. Occasionally, the application experiences bursts of over 500 simultaneous connections. Even though, the server showing less than 10% CPU utilization and about 75% of RAM still available, I am encountering "connection refused" errors. I can see Windows Performance counter TCPv4 / Connection Failures change when this happens. There is no antivirus deployed during my test, and Windows defender is off. i have seen similar issues on Windows 2019 and 2022 also. I suspected SynAttack detection, but the TCP diagnostic counters for SynAttack detection dont know any values. It appears to me that there is some Windows OS limitation that causes this issue. Does anybody encounter this situation before?
About recommend hardware for the next version of windows in the future
I am a loyal Microsoft Windows user. Now, I have a small problem: I want to upgrade my computer to Windows 11 but my hardware does not meet the requirements; I need to upgrade the hardware for it. I am also a loyal AMD Threadripper Pro user. I see the minimum requirement is Ryzen Threadripper Pro 5945WX. I want to ask when Windows 12 is released, will it still be supported? And Win 13, Win 14 in the future. I do not have the conditions to change the hardware every time there is a new version of Windows. If it is not supported, I may have to learn to switch to another operating system. P/s: Don't ask me why it have to be Ryzen Threadripper Pro or Recommend another one, Just say I want to use Ryzen threadripper pro to experience playing Pikachu in 1080p mode more smoothly.Windows Research Kernel Bring it Back!
I think it is time to revive the Windows Research Kernel! We need the community to be able to understand what is going on without letting everything out of the bag. The last version available was v1.2 which was based off of the kernel for Windows XP and Windows Server 2003 SP2. We need a modern release for development, education, and security research. Who is with me?
Demote a 2019 server - problem
I want to demote one of our 2 DC's in preparation for server replacement. Replication between the two works fine and both DNS's are synced and up-2-date. But when I run the wizard, I need to check that "This is the last DNS server" which is not true. If not, I can't proceed to the next step (Next becomes greyed out). As an experiment, I did this last week and it resulted in a domain where no client could logon, and no file shares was working on the remaining DC/File server. So I restored both backups to get back in business. I do not want to repeat this again. I have browsed the complete DNS tree for the forward zone and everything looks fine to me (SRV, NS etc records)
dbgeng.h: GetTotalNumberThreads Returns Incorrect Thread Count (According to DAC)
When writing custom extensions for Windbg to analyse user-mode crash dumps (using the IDebugSystemObjects4 interface provided by dbgeng.h), IDebugSystemObjects4-->GetTotalNumberThreads returns a smaller number than Strike/SOS. There is no documentation about where IDebugSystemObjects4 gets the thread count from -- it just states: The GetTotalNumberThreads method returns the total number of https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/controlling-threads-and-processes for all the https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/controlling-threads-and-processes in the current target, in addition to the largest number of threads in any process for the current target. (Emphasis mine.) Below is an example output from Windbg: 0:000> <Custom Windbg Extension Method Here> Getting IDebugSymbols... Getting IDebugSystemObjects... Getting GetTotalNumberThreads... Total Threads: 581 Largest Process: 581 Frames: 32 0:000> !threads ThreadCount: 587 UnstartedThread: 0 BackgroundThread: 26 PendingThread: 0 DeadThread: 47 Hosted Runtime: no Note that the IDebugSystemObjects4-->GetTotalNumberThreads method is returning 581 threads but Strike/SOS is returning 587. For what it's worth, https://github.com/dotnet/diagnostics/blob/6a90923439dc43693f2a2fc8766b3cdb2c4dd366/src/SOS/Strike/strike.cpp#L4358 -- which is, presumably, a different source than IDebugSystemObjects4 is getting the thread count from. Is this a bug in dbgeng.h? If not, is it because IDebugSystemObjects4 ignores finaliser threads; whereas those are not ignored when committed to the DAC? Also, sorry if this is the wrong place for this, I was thinking Windows SDK-related questions/bugs would fall under "Windows OS Platform".
Questions about Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 support plans.
I have known that all the supports of Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 has ended at Janauary 9th, 2024, the date where mentioned in Microsoft Lifecycle Policy. But I have found some updates which released after Janauary 9th, 2024, in Microsoft Update Catalog, and these updates will provide to these Operating System which have 4 years ESU license. So why does Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 still can receive these updates after Janauary 9th, 2024? Does these Operating System has any additional support plans after that day? When will these OS doesn't receive any updates?
