Forum Widgets
Latest Discussions
"Can't access Recall right now"
I've enabled Recall feature on Windows 11 Pro (26120.3380) on my Surface Laptop 7 with Snapdragon X Plus. I was able to use it for a while, but then since some recent update (or maybe after I changed the primary login email for my Live.com account), it stopped working. Even though it's turned on and appears to be saving snapshots (it shows it's using disk space), I can't access any snapshots. I tried turning the feature off and on using command line (Recall doesn't show up as one of the features I can enable/disable on "Turn Windows Features on or off" program). Also tried deleting all snapshots, disabling/re-enabling Recall, etc. None of them fixes this. I also get this message sometimes, even though I have Bitlocker turned on:Is there a way to fix iPhone stuck in SOS mode?
Hi everyone, this afternoon my iPhone 15 Pro (iOS 17.6) suddenly got stuck in the SOS emergency call screen. I was using TikTok when the screen suddenly turned black and then jumped to the SOS screen, with "Emergency Call"flashing at the top and a red "Connecting to Rescue Center" progress bar at the bottom, but I couldn't do anything at all. Is there a simple way to fix iPhone stuck in SOS mode? I couldn't press the side button to turn off the phone, and I couldn't press and hold down the volume button to bring up the SOS option. After a reboot, the situation repeats itself, and attempts to connect to Wi-Fi and mobile data are ineffective. The phone is still at 30% battery and is not in low battery mode. This is the third time this week that a similar lag has occurred, but the first two reboots recovered normally.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.
Updating Failed when Attempting Feature Update 26340.9212
Hello, I was prompted to restart because of a Windows Update and went through the update process, but it failed. Now, I have a perpetual "Retry All" at the top of the Windows Update screen. Each time I press retry, I get this error: "We didn't find any updates that are published for your edition at this time. We'll try again when the next scheduled update is published. I am currently using Windows 11 Pro Insider Preview, Build 26300.9032.ge_prerelease_im.260726-0034. The Troubleshooter for Windows Update also isn't launching. How can I fix these problems?
Insider build 29648.1000 keeps failing to install
Hey everyone, I'm stuck on this one. Every time I try to install the latest Insider build—29648.1000—it just fails. I tried installing it through Windows Update first, and when that didn't work, I downloaded the update manually and mounted it. Same result. Current build is 29617, running Pro on a Lenovo IdeaPad. No error code that's been helpful so far. Anyone else dealing with this or have any idea how to get past it?
Windows 11 25H2 upgrade fails after restart with 0xC1900101-0x20017
Hello, I am having trouble upgrading my Windows 11 Insider Preview installation to Windows 11 version 25H2. Current system: Windows 11 Home Insider Preview Current build: 26300.9032 Target: Windows 11 version 25H2 Windows Update successfully downloads and begins installing the 25H2 update. It eventually asks me to restart. After restarting, Windows processes the update but then rolls back and returns to the previous installation. Windows Update reports: Install error: 0xC1900101-0x20017 I checked Device Manager and there are no devices showing a yellow warning or exclamation mark. I also checked: C:\$WINDOWS.~BT\Sources\Rollback I found setupact.log and setuperr.log there. Some relevant errors from setuperr.log are: CSetupHost::CheckSetupMutex(1263): Result = 0x8007052 CSetupPlatform: Executing Sync commands: Failure while executing command Rollback: Executing Sync commands: Failure while executing commands. hr = 0x80004005 CSetupPlatformPrivate::Rollback: ExecuteRollback failed. Failed to merge telemetry file: hr = 0x80070057 Could someone please help identify what is causing the rollback and what I should try next? Thank you!
Unable to activate Windows Insider build 26340
Hello all, I've been in the Windows Insider program since Windows 11 was in prerelease testing. A couple months ago, my install went poo (It wouldn't boot all the way; I think it was a graphics driver problem). I didn't touch it for a month or two, but I just reinstalled windows (first to the retail version ISO, then over to an insider build), but Windows is refusing to activate. I tied a beta build, then I tried the latest experimental build. Yes, I am signed into my microsoft account with my Insider email but it says no hardware on my account has a windows 11 install that I can reinstall (I think that's what it said). I would think that all insider builds should be able to activate without a retail key since we're testing windows for MS. I shouldn't have to purchase a new key, should I? I'm running build Win11 Pro 26340. I've always run Pro windows (or Home Premium in windows 7 days). I just tried getting help from Windows support, but the agent said they can't help with Insider installtions and directed me here. I did try searching for my issue, but nothing seemed relevant. Any ideas? Dominic
