This issue occurred after I and other users installed KB5101684, disrupting File History.
My question Hello,I would like to ask whether other Windows 10/11 users have experienced the same File History problem, and I hope Microsoft will seriously investigate it. My laptop runs Windows 11 25H2. Before installing KB5101684, File History worked normally. After installing KB5101684, I noticed: Last backup does not update correctly. Previous Versions still shows no previous versions. Files are still written to D:\FileHistory\..., but File History does not properly update its backup information. Folders such as Desktop and Favorites have their modification dates changed even when their contents were not changed. I did not manually change File History settings, registry settings, or delete Event Viewer entries. I also experienced a similar problem on my Windows 10 22H2 desktop after installing KB5120249. In short: Windows 11 25H2 → KB5101684 → File History problem Windows 10 22H2 → KB5120249 → File History problem Could these updates have introduced a File History regression? Microsoft, please investigate whether these KB updates are related to the incorrect backup timestamps, missing previous versions, and unexpected File History behavior. Please do not simply ask users to reset File History or reselect the backup drive. Users need to know what is actually causing the problem and whether Microsoft will provide a fix. If other Windows 10/11 users have experienced the same issue, please share your Windows version, KB number, when the problem started, and whether files are still being written to the FileHistory folder. Please also consider sharing this post with other Windows users or Microsoft technical staff so this issue can receive proper attention. Microsoft, please investigate this issue seriously and provide a clear explanation and solution. Thank you. The following are the problems that users and I encountered.
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.
Windows 10 Pro Digital License Not Reactivating After Replacing Motherboard with the Same Model
윈도우 7에서 윈도우10으로 무료 업그레이드후 노후환 된 메인보드를 교체를(동일 모델) 하였는데 정품인증이 안되고 있습니다. 더이상 어떻게 해야 할지 모르겠는와중 여기를 마이크로 소프트 지원팀에 채팅으로 대화하다 알게 되어서 글을 남깁니다. 현재 확인한 사항: 윈도우 버전 windows 10 pro (Retail), 마이크로 소프트 계정-> 장치 이전 pc 및 현재 pc 둘다 등록이 되어있는걸 확인 1. 설정-> 정품인증 -> 문제해결 = 해결 X 2. 설치ID를 통한 시도 해결 X I upgraded from Windows 7 to Windows 10 for free. Recently, I replaced my aging motherboard with the exact same model, but Windows is no longer activated. I was not sure what else I could do, and I learned about this community while chatting with Microsoft Support, so I decided to post here. Current information I have confirmed: - Windows version: Windows 10 Pro (Retail) - Microsoft account > Devices: Both my previous PC and my current PC are registered. Troubleshooting I have already tried: Settings > Activation > Troubleshoot: Did not resolve the issue. 2. Tried activation using the Installation ID provided by Microsoft Support: Did not resolve the issue. The Windows 7 product key I originally used is still available, but entering it in Windows 10 results in an activation error. I would like to know whether my previous Windows 10 digital license can be transferred or reactivated on the replacement motherboard.Issues with syncing calendar from outlook calendar in taskbar
I am wondering how I can sync a specific calendar from outlook to be the one that the events get pulled from to appear in the taskbar calendar that is displayed when clicking the date/time tool. Currently the calendar that appears when I click the date and time section is blank, and trying to make a new event from that popup does not save anything. When go into the outlook calendar app, I can see the multiple email accounts and their respective calendar, but yet no events from these calendars show up when looking at the calendar popup from the taskbar. When trying to make an event in this calendar popup, it even gives me the option to save the event to one of my outlook accounts (the gmail account I have integrated), but does not successfully save any event anywhere. I am wondering what is required to be able to see the events from my outlook calendar in this popup, and to be able to quickly and conveniently make events from this taskbar popup and have them save to my actual outlook calendar. Including a screenshot of the calendar in taskbar that I am requesting help with incase of any confusion.update KB5120249 on a desktop Windows 10, the file history time cannot be synchronized correctly.
My problem: https://learn.microsoft.com/zh-tw/answers/questions/5972262/windows-11-kb5101684 Not only after installing KB5101684 on my laptop, file history timestamps fail to sync correctly, but even after installing KB5120249 on my desktop, file history timestamps fail to sync correctly. I don't know what Microsoft is doing? It's so frustrating! Please, Microsoft, fix this quickly!High CPU usage by Antimalware Service Executable (Windows Defender) on every login
Hello, I am experiencing a persistent issue with Windows Defender. The background process Antimalware Service Executable (MsMpEng.exe) consumes extremely high CPU usage every time I log in, making the system nearly unusable. The only temporary workaround I have found is disabling real-time protection, which immediately stops the high CPU usage. However, I do not want to permanently disable protection for security reasons. Here is what I have already tried and what did not help: Reducing Windows Defender CPU usage from 20 percent to 5 percent did not help, the process still uses most of the CPU. Excluding my drives from scanning did not help, I excluded both drives I use but Defender still appears to be scanning something in the background. Removing Windows Defender entirely seems like the only effective solution, but I understand this is not recommended since it is a built-in system component and could cause system issues. For several months now, my routine has been logging in and manually turning off real-time protection just to be able to use my system, which is not a sustainable or secure solution. Is there any way to resolve this issue while keeping Windows Defender enabled? Any guidance or recommended troubleshooting steps would be greatly appreciated.
