CLAT (for 464XLAT) for lan and wireless
Hi, I've seen this blog post from three years ago: https://blogs.technet.microsoft.com/networking/2017/07/13/core-network-stack-features-in-the-creators-update-for-windows-10/ Could you please provide an update on when (of if already how) to configure the clat for connectivity to IPv6 only networks? There is a public hotspot network around here that works perfectly fine with android phones, and also mostly with windows, but some apps are failing because of hard coded IPv4 addresses. And we're also planing to have IPv6 only networks for our selves, so information on this would be very appreciated. - agowa338Any updates on the Xbox Game Core?
The technology in Windows kernel or core, called Game Core. which lets PC users install the Same Xbox games on their Windows 10 systems. Microsoft tested this with the game State of Decay 1. but that's just it, no news for months. the Kernel of Windows 10 has seen lots of changes such as the Linux kernel being added to it and now the compatibility with Xbox kernel. I wish i could find a Microsoft docs about this feature but only 3rd party websites post about this, not sure why! the news articles covering it: https://www.kitguru.net/gaming/operating-systems/matthew-wilson/microsoft-appears-to-be-bringing-xbox-game-compatibility-to-windows/ https://www.thurrott.com/games/200140/microsofts-evolving-gaming-strategy-takes-a-giant-step-forward
Can't sign kernel drivers for Windows 11 & 10
Hi, We recently purchased an EV certificate to sign our software kernel driver, however, when trying to load it in Windows 10 it fails with code 0x800B010C aka CERT_E_REVOKED - A certificate was explicitly revoked by its issuer. We checked the driver with "signtool verify /v /all /pa" as suggested by our cert provider and everything is still valid. We followed these instructions https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release We've also tried contacting Microsoft's dev support by MS closed it down recently and they're not replying anymore... Any help would be appreciated, A.
Server Reboots Kernel 41
Hello Have a HP Proliant DL325 with Windows 2019 Server installed. The server keeps rebooting daily around 3 times,. Event ID 41 Power Kernel Issue. HP could not find anything within their system logs. I know its a shot in the dark. I have ran HP Smart Manager Updates recently but still happens. The server is connected to a HP Protector UPS. However, the logs on this do not show anything. During reboot someone onsite said a message appeared saying server failure. Any guidance appreciated.windows kernel driver debug setup WDKRemoteUser account keeps asking for password on HyperVM machine
Hello, i am using Visual Studio 2022 Professional edition, and setup a HyperVM machine to debug my kernel driver that i am developing. After provisioning the installation for kernel debug via the VS VM configuration. For a limited time everything works, but when i restart the VM, my os is waiting for me to login / choose a user account to log in. I couldn't find any way to correctly configure it to always logon as WDKremoteUser without asking me for a password, that i don't know and cant find anywhere. Any thought appreciated, on how to fix this. Thank you.
Bug in kernel Filter Manager
Hi, I encountered a use case when FltGetFileNameInformation with "Normalized" returns a wrong path. The setup: A Win 10 VM running on a Win 10 host. A network share mapped to a drive letter in the VM to the host (example: map Z: to \\192.168.44.1\e$). browse z: and try to run a file. I have a filter manager that calls FltGetFileNameInformation(.. FLT_FILE_NAME_NORMALIZED | FLT_FILE_NAME_QUERY_FILESYSTEM_ONL, ...) in PostCreate callback. Behavior: (the description below is using a tester, the issue occurred during Win 10 explorer operations) A user space process opens a file (FileHandle), then another open is performed: InitializeObjectAttributes(&ObjectAttributes, (PUNICODE_STRING)&NullFile, OBJ_CASE_INSENSITIVE, FileHandle, NULL); Status = ZwOpenFile(&NewFileHandle, GENERIC_READ, &ObjectAttributes, &IoStatusBlock, FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE, 0); In the PostCreate callback the FileObject has a FileName with length 0. The RelatedFileObject is the one from the first create (FileName \;z:\........) The result of FileNormalizedNameInformation is: kd> dx -r1 ((cyvrfsfd!_FLT_FILE_NAME_INFORMATION *)0xb16311dc) ((cyvrfsfd!_FLT_FILE_NAME_INFORMATION *)0xb16311dc) : 0xb16311dc [Type: _FLT_FILE_NAME_INFORMATION *] [+0x000] Size : 0x40 [Type: unsigned short] [+0x002] NamesParsed : 0x0 [Type: unsigned short] [+0x004] Format : 0x1 [Type: unsigned long] [+0x008] Name : "\Device\Mup" [Type: _UNICODE_STRING] [+0x010] Volume : "\Device\Mup" [Type: _UNICODE_STRING] [+0x018] Share : "" [Type: _UNICODE_STRING] [+0x020] Extension : "" [Type: _UNICODE_STRING] [+0x028] Stream : "" [Type: _UNICODE_STRING] [+0x030] FinalComponent : "" [Type: _UNICODE_STRING] [+0x038] ParentDir : "" [Type: _UNICODE_STRING] Note that the returned path is the device path (not the file path) Root cause: After Microsoft added support for FileNormalizedNameInformation the code of FltpGetFileName changed (in Windows 8.1) In Windows 7 FltpGetFileName callced FltpQueryInformationFile, and this call succeeded the the result was Ok (no bug). In Windows 8.1 (and Win 10): 00 979cf6f4 89097cda fltmgr!FltpGetFileName+0x199 01 979cf704 89094f62 fltmgr!FltpGetOpenedFileName+0x18 02 979cf720 89097d5c fltmgr!FltpCallOpenedFileNameHandler+0x8a 03 979cf73c 89098505 fltmgr!FltpGetNormalizedFileNameWorker+0x16 04 979cf754 89095765 fltmgr!FltpGetNormalizedFileName+0x19 05 979cf76c 890958a8 fltmgr!FltpCreateFileNameInformation+0x81 06 979cf780 8907fe1e fltmgr!CreateTemporaryFileNameInformation+0x4e 07 979cf7b0 8907ffa3 fltmgr!FltpGetFileNameInformation+0x61e 08 979cf7d8 b1917e0d fltmgr!FltGetFileNameInformation+0x12b FltpGetFileName sends a QueryInformation IRP with InfoCalss set to Normalized. This request fails with STATUS_NOT_SUPPORTED. The problem is that the code in FltpGetFileName ignores the failure and reaches an if statement: if (Data && FltpOperationFlags(.....) & 2 && PostOperation && !FileObject->FileName.Length) { *SystemBuffer = 0; // SytemBuffer points to FILE_NAME_INFORMATION struct // Code that concatenates the device name to the path resolved (which is empty in this case because it failed) return STATUS_SUCCESS; } The function meant to try first with Normalized and if not supported try with Opened but the problem is that after it returns not supported for Normalized is returns a faulty result. Any chance there is a Microsoft engineer here that could take a look at this. Thanks, AminMicrosoft Driver Latency
Hi I thought I would ask here about latency in Windows OS Kernel level. I have confirmed on two machines I own, and with several people online with different gear that we are all experiencing the same issues. Using the app LatencyMon to check on things we found that the Windows drivers seem to trip up. This is regardless of what hardware we use also. It also is exactly the same from Windows 10 to Windows 11. My old desktop: Phenom II era 8 core FX series CPU with 12 GB ram SSD OS drive. RX580 GPU I have reformatted and freshly reinstalled Windows 10 Pro updated every possible thing I could and with only a keyboard and mouse connected no other apps except LatencyMon and when I check I get high latency from USBport 1.1 and 2.0, HDAudiobus, and others. My laptop: 9th gen i7 12 core CPU 16 GB Ram RTX 2070 GPU 8 GB DDR6 2 ssd drives M17 Alienware machine.. Has LatencyMon and the software from Dell, Intel, and Alienware on it. All of those directly linked to the manufacturer for ongoing updates. Everything is as up to date as possible. Firmware, drivers, and anything else. I run LatencyMon and the same exact drivers are hitting well into the red zone. It may not be enough with no other apps accessing these drivers, but it isn't helping things run smoother. I have been trying to do my best rooting out the actual issues. From all I read many different softwares can trigger that ever present system wide latency, not just one particular app. So my thinking is: what is the one constant that all users facing this have in common. We all use the Windows OS. Systinternals has Process Explorer that helps show more details, and years back found that 2 drivers had been massive issues. Both doing with HD Audio and HD Video from DirectX. Direct X sadly still appears at times. Is it possible to treat the Windows Kernel drivers as real-time to see if that might stop or greatly reduce these latency issues. Also, can't the Kernal keep track of latency and before it becomes an issue immediately alert the end user to the situation, with the trouble making drivers, and other issues that triggered them to go into the red... Think UV meter for sound. Instead of getting distortion or clipping you get a heads up an issue is happing that if corrected now may avoid system crashes and latency issues. With this information we as the end users are able to share it with any 3rd party app devs and Microsoft so hard working, over worked, under paid kernel devs can hopefully fix things also more accurately. I first encountered system wide latency issues soon after we started going HD Video and HD Audio in Windows 7. Unfortunately this issue has not gotten any better over the years. And, I am currently using Windows 11 Beta on my laptop. It has the exact same issues. Changing the shell is little more than changing the paint on a car. Or, curtains in wondows of a house. Real features would be eliminating the ongoing latency issues. Adding components that connect to actual manufacturers sights allow us to download drivers or have the OS alert us they are ready. If Dell, Intel, and others provide them so the maze of drivers are properly updated and saves untold users from Drive Easy and the like as well as reduce the endless posts to Microsoft about the never ending latency issues... A friend online has a much nicer rig than my laptop, also in Windows 11 beta - I think gen 11 i9 10 or 12 core cpu, 32 GB ram, RTX 3090 we are talking top of the line here. Exactly the same latency issues. This is probably one of the biggest issues to overcome for Windows. Any chance that is possible? Thanks for reading my book here, I am a little frustrated with this, and Linux is looking nicer everyday. Jon
