Any 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
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, Amin
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.
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. - agowa338
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.
