Forum Widgets
Latest Discussions
Secure Time Seeding / W32Time Large Time Correction Issue
Hello everyone, I’m investigating an unusual time synchronization issue with Windows 10 IoT Enterprise LTSC involving W32Time and Secure Time Seeding (STS) in a closed network, and I’d appreciate any guidance or insights from the community. In our environment, time.windows.com resolves to our internal IP/NTP server. The server receives NTP requests and returns a valid response with the correct time. Network monitoring confirms that both the request and response are working correctly. However, we observed an unusual behavior: If the system clock is set to 2035 or earlier, W32Time successfully corrects the time. If the system clock is set to a much later date, such as 2056, W32Time receives the correct NTP response but does not update the system clock. This behavior has been observed in both open and closed networks. We have already tried: Configuring MaxPosPhaseCorrection and MaxNegPhaseCorrection to 0xFFFFFFFF. Enabling UtilizeSslTimeData = 1. Unregistering/registering W32Time. Stopping/starting the Windows Time Service. Reconfiguring the NTP peer. Running w32tm /resync. Verifying NTP traffic and responses using network monitoring. We are also trying to understand how Secure Time Seeding (STS) works in this scenario. On an open network, STS appears to obtain and cache trusted time, which may help Windows recover time while offline. However, in our closed network, where time.windows.com resolves to our internal NTP server, STS does not appear to establish trusted time in the same way. Questions: Is there a W32Time or Secure Time Seeding limitation that prevents very large time corrections, even when MaxPosPhaseCorrection and MaxNegPhaseCorrection allow them? Why does synchronization work at 2035 or earlier but fail around 2056? Is the 2035/2056 behavior related to timestamp validation, NTP, STS, certificates, or another Windows limitation? Does STS require Microsoft's actual time infrastructure, or can an internal NTP server participate? Does resolving time.windows.com to an internal IP prevent STS from establishing a trusted timestamp? Is there a supported configuration on Windows 10 IoT Enterprise LTSC to treat an internal NTP server as a trusted time source? Are there specific W32Time event logs, registry settings, Group Policies, or diagnostics we should check when an NTP response is received but not applied? Accurate and trustworthy time is critical because timestamps are used for offline operations. Any guidance on whether this is caused by W32Time large-offset handling, Secure Time Seeding, timestamp validation, or an interaction between these components would be greatly appreciated.
Win11 25H2 File Explorer preview pane displays bitmap images incompletely
The system version is Windows 11 25H2 (Build 26220.9022). Since the update on August 1, 2026, the File Explorer preview pane has been unable to fully display bitmap images. Regardless of whether the image is in landscape or portrait orientation, a gray gap appears at approximately the bottom 2/3 to 3/4 of the preview area. The position of this gap remains fixed relative to the screen and is independent of the image’s aspect ratio. The images open normally in other applications; this issue occurs exclusively in File Explorer’s preview pane, causing inconvenience when viewing images on a daily basis. I would like to confirm whether other users are experiencing the same problem.Windows Insider Updates will not download
I have been stuck on 22635.5015 for over a year now, not receiving nay updates. I finally started to receive updates after I switched to the Beta channel instead of the Release preview I was on, but I have been unable to install those updates. I go through the whole update process and my PC restarts, but when I get back to the desktop I see that the update failed to install.
Unable to update Windows, and I am unable to unroll the system too
I am unable to update Windows; it's not downloading beyond 99% in the update window. Brattary drining is high, so I want to unenroll the current device from the Windows Insider program for now, which I am unable to do. When I unroll it, it's showing unrolling is queued but not unrolling. Help me to unroll this device and get me to a stable update by Windows so I can work smoothly.
