Forum Widgets
Latest Discussions
dbgeng.h: GetTotalNumberThreads Returns Incorrect Thread Count (According to DAC)
When writing custom extensions for Windbg to analyse user-mode crash dumps(using the IDebugSystemObjects4interface provided by dbgeng.h), IDebugSystemObjects4-->GetTotalNumberThreads returns a smaller number than Strike/SOS. There is no documentation about whereIDebugSystemObjects4 gets the thread count from -- it just states: The GetTotalNumberThreads method returns the total number of threads for all the 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 theIDebugSystemObjects4-->GetTotalNumberThreads method is returning 581 threads but Strike/SOS is returning 587. For what it's worth, Strike/SOS gets this data from the DAC -- which is, presumably, a different source thanIDebugSystemObjects4 is getting the thread count from. Is this a bug in dbgeng.h? If not, is it becauseIDebugSystemObjects4 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 updateswhich 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?
Automatic installation of Roots Updates
You can use the registry parameter to redirect the source of root certificate updates: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate "RootDirURL"="d:\......." Is it possible to automatically distribute certificates of intermediate certification authorities in this way?
Invalid requesting-user-name value after system reboot (IPP Everywhere)
When I add a IPP Printer, it works fine until I restart OS, after system reboot the requesting-user-name contains WORKGROUP\VM132786998$ so it's domain\computerName$. And the user cannot be correctly recognized. Steps to reproduce it: 1. Add IPP printer 2. Print Test page 3. Restart system 4. Print Test page Current result if inspecting by Wireshark: at point 2. requesting-user-name contains correct "Administrator" value at point 4. requesting-user-name contains incorrect "workgroup\VM132786998$ Expected result: in both cases correct value Administrator must be present. Currently only restart print spooler or recreating printer solves the issue. (See attached wireshark captures before and after print spooler restart) Note: The issue is not reproducible in build 22H2 22621.3447. I'm able to reproduce it in 23H2 22635.4076. Same error is observed here (comment from Douglas Kosovic): https://learn.microsoft.com/en-us/answers/questions/1428508/ipp-everywhere-ipp-2-0-server-basic-authentication Attached screenshots from wireshark captures when it's happening and after restarting Print Spooler.
ACPI EC OpRegion location
Hello, the ACPI specification defines OpRegions for ACPI bytecode to interact with devices, one suche device being the Embedded Controller. After looking at some example ACPI tables, it seems that Embedded Controller OpRegions can be defined anywhere inside the ACPI namespace, and not just inside the Embeeded Controller device scope. What is the Windows kernel policy for such OpRegions? Which Embedded Controller will be used to handle them (if any)? Thanks, Armin WolfMicrosoft's IPP driver keeps printing forever
Hi. I am not sure if this is the correct forum, but anyway. I have the following situation. I have a print server that I want to make compatible with the Microsoft's IPP class driver. This print server has multiple queues, and I am now in a state, where I can add each queue as a printer in Windows in combination with the IPP class driver. All good so far. The issue is, that when I delete one of the queues on the server, and I try to print some page through the corresponding IPP printer in Windows that I added earlier, the IPP client will try to retry the job every 10 seconds (or so) until I manually cancel it. The client behaves like this regardless of any error code I send to it from the server. I essentially tried all meaningful IPP error codes and all meaningful HTTP error codes. Still, IPP client keeps trying to send the job. Am I missing something? Is there a way how to force the client from the server to stop printing? The absence of any limit on the requests is quite inconvenient because multiple clients can be misconfigured and unnecesarilly overload the server. Thank you for any answer. PS: I am trying this on Version 10.0.19045 Build 19045
Windows pro for workstation for music production
Hi all Im a music producer and maker mixer and master. Today im working on Windows 11 home Z980 13700k ddr5 5600 990 pro 980pro 870 ect disks I have quite heavy projects and thinking of change to Windows 11 pro for workstation that have and feel alot more stable when it have another memory type and it fix bad sektors with taking samt data from another palce. just this feel that ist more stable and very eaven box to work in for music DAW and hybrid setup. So is there any that have tryed Win 11 pro for workstation, and what hardvare is best for the OS to work properly?"NET USE" help/syntax message has a little mistake
There is a little mistake in "NET USE" help/syntax message has a little mistake since probably quite a long time: seen in Windows 10 , 11, Windows Server 2016, 2019. Hope somebody from Microsoft is reading this. This is what we get on typing "net use /?" The error is in the line [/USER:[username@dotted domain name] It should have been [/USER:username[@dotted domain name]] Thanks to anyone reporting this to Microsoft.
