Getting account back after hack
I have lost my account to a hacker, and whenever i try to do the account recovery form i get a response the same minute that they dont think its me, i still have the gmail thats connected to the account but cant use that to prove that i am the owner, since the recovery mail has been moved How can i prove that the email the account is registered under wants to change the password? Im only writing here since i am running out of options
Windows 11 passkey QR flow: Android shows error, Windows sends 01 00 instead of Shutdown 00
Hi all, We see the following on every Android phone we tested when creating or using a passkey through the QR code (hybrid) flow from Windows 11. The operation succeeds on the PC and the passkey works, but at the end the phone shows "Something went wrong. Restart the process on your other device to try again." An iPhone shows no error. Reproduced on: - Windows 11 25H2, builds 26200.9711 (Enterprise, managed) and 26200.8875 (Pro, unmanaged, no policies) - Edge 157 and Chrome (both hand the flow to the Windows WebAuthn API) - webauthn.io and Microsoft Entra ID, attestation none and direct - Samsung, Pixel and OnePlus phones, Google Password Manager and Samsung Pass - also on a mobile hotspot without VPN or proxy What the logs show: Windows (Event Viewer > Microsoft > Windows > WebAuthN > Operational, verbose events 2332 and 2333). The post-handshake messages are logged as padded plaintext (32 byte granularity, last byte = number of zero padding bytes). The final write message after every registration and authentication is: 01 00 00 00 ... 00 1D After removing the padding the payload is `01 00`. In caBLE v2 the message types are kShutdown = 0, kCTAP = 1, kUpdate = 2, kJSON = 3 (Chromium, device/fido/cable/v2_constants.h). Chromium ends a session by sending `[0x00]` (Shutdown) and waiting for the phone to close the tunnel (fido_tunnel_device.cc). Windows sends `[0x01, 0x00]`, which is a CTAP message with the invalid command byte 0x00. Android (adb logcat, Google Play services 26.43.30): ``` [HybridMessageProcessor] Received CTAP message [HybridMessageProcessor] processing the CTAP message failed for invalid data Received invalid CTAP command ... can't find command for CTAP request [HybridResponseHandler] Generic hybrid error: INVALID_CTAP [HybridErrorFragment] HybridErrorFragment is shown ``` So Google Play services rejects the final Windows message as INVALID_CTAP and shows the error screen, after the credential has already been created or the assertion returned. A very similar bug was fixed in libwebauthn (desktop closed the tunnel without a proper Shutdown): https://github.com/linux-credentials/libwebauthn/pull/310 Questions: Does anyone else see this, with which Windows build and phone? Can someone from Microsoft confirm whether the missing Shutdown message is known and when a fix is planned? Is there a supported workaround until then? Thanks SeverinHow does Sleep mode drain more battery than actually using the laptop?
I've noticed that my laptop's battery drains faster when it's in Sleep mode than when I'm actually using it, which seems completely backwards. Could someone explain why Sleep mode would consume more power than active use, and whether this is a settings issue I can fix?Windows Error 0x80070005: Unlock Xbox Downloads
If you are trying to install or update software on PC and the process immediately freezes with code 0x80070005, it is because the underlying Windows security system has locked its own file folders. When an OS update shifts folder ownership settings behind the scenes, the system basically strands your desktop interface and rejects new file creation. You can clear this storage block and restore access natively using either of the two independent methods below. Restore Access Permissions to the Local AppData Folder You can force Windows to restore full write privileges by updating folder ownership permissions: Open the Run dialog by pressing Windows Key + R, type %localappdata%, and press Enter. Navigate up one folder level in File Explorer, right-click the Local folder, and choose Properties. Click into the Security tab, click Edit, select your user account, check Full Control, and click Apply and OK before restarting your PC. For secondary drives like a D: or E: partition, go straight to the root directory, delete the application data folders, recreate them manually, and restart the environment. Reset System Security via Command Prompt Running a system configuration script can clear locked registry keys and permission conflicts: Open Command Prompt as an administrator and run this command string to reset your security configurations: secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose Let the script run completely and restart your computer once the terminal finishes. If issues persist, go to Settings, click through Apps and Installed Apps, locate the target package icon, and select Advanced Options to run the built-in Repair and Reset tools. Manually resetting those folder privileges or running that terminal script usually untangles the loop right away. Hopefully, forcing the OS to respect the standard access path gets the desktop environment running normally again without any more freezing.
Azure Container Linux (ACL): making immutable infrastructure practical at scale
Where we left off… At Microsoft //Build 2026, we introduced Azure Container Linux (ACL) , an immutable, container-optimized OS for Azure Kubernetes Service (AKS) bringing greater consistency, reduced operational overhead, and a stronger default security posture to your nodes. Since GA, we’ve focused on helping customers operate ACL more effectively as their environments scale and security requirements evolve. Today, we’re announcing the next set of capabilities: simpler fleet scaling, hardware-backed protection for sensitive workloads, and new ways to assess code integrity and software vulnerabilities. These updates bring more of ACL’s benefits into your day-to-day operations. We’re also sharing what’s next for OS updates, an important part of making immutable infrastructure practical at scale. Stronger security shouldn’t complicate fleet management As Kubernetes environments grow, small differences between nodes become harder to track. Various platform components may install or update software independently, and non-deterministic package updates can cause hosts that started from the same baseline to gradually diverge over time. Direct changes made during troubleshooting can further contribute to this drift. These differences complicate upgrades, make incidents harder to reproduce, and create uncertainty about what is running in production. ACL addresses these challenges with an image-based operating system and a read-only /usr filesystem backed by dm-verity. Core OS components, including system binaries and kernel modules, remain consistent with the image you deployed and across your fleet, helping prevent OS-level configuration drift and potential tampering. A minimal package set also reduces the number of components you need to maintain and the potential exposure to vulnerabilities in packages your workloads don’t need. Node consistency is the foundation, but scaling a fleet also means matching capacity to changing workload needs. As your workloads grow, managing capacity shouldn’t mean spending more time configuring node pools. ACL now supports node auto-provisioning (NAP) in AKS, which automatically selects VM sizes and provisions nodes based on workload resource requirements. This is particularly useful for agentic workloads, where agents can launch parallel jobs and short-lived tasks that create unpredictable compute demand. NAP reduces manual node pool configuration and management, so you can automatically scale with demand while retaining ACL’s immutable OS protections. See Configure NAP with ACL for prerequisites and setup instructions. Layering OS protection with confidential computing and code integrity ACL provides layered protection for the operating system. As AI helps attackers analyze newly disclosed vulnerabilities and develop exploits faster than ever, the time between CVE disclosure and active exploitation continues to shrink. Immutability helps protect core OS components from modification, while SELinux restricts process access to limit the impact of a potential compromise. Trusted Launch protects the boot chain, with Secure Boot validating a signed Unified Kernel Image (UKI) that bundles the kernel, initial RAM disk, and kernel command line. Together, these controls help defend against tampering, reduce opportunities for persistence, and contain threats. Today, we’re extending these OS protections to confidential virtual machines (CVMs), combining ACL’s immutable foundation with hardware-backed protection for data in use on both Intel TDX and AMD SEV-SNP platforms. We’re also introducing FIPS-enabled CVM images for workloads that require FIPS-mode cryptography, making the ACL the only OS on AKS to offer this configuration. Alongside these protections teams need assurance that executable code comes from trusted, integrity-protected sources. Integrity Policy Enforcement (IPE) addresses this need by evaluating file-backed execution against policies based on a file's integrity properties. Originally developed at Microsoft to enforce code integrity across Azure infrastructure, IPE became part of the mainline Linux kernel in version 6.12. IPE complements SELinux by answering a different question. While SELinux controls what a process is allowed to do, IPE helps verify that the code being executed originates from trusted sources. Together, they provide both access control and code integrity protections. On ACL, support for IPE is currently focused on evaluation through an optional audit mode. ACL includes an IPE policy that permits file-backed execution only from dm-verity-backed devices with trusted root hashes. When audit mode is enabled, IPE records execution attempts that would violate the policy without blocking them, helping operators understand where workloads or operational practices diverge from a trusted-execution model. To learn more about enabling IPE audit mode in ACL and inspecting the resulting logs, see Enabling IPE for ACL. An immutable host still needs to fit your security assessment process When it comes to securing your fleet, platform teams need to assess host configurations, inventory software components, and identify known vulnerabilities using their existing tools and processes. The ACL CIS Benchmark and embedded software package inventories, published in SPDX format, support these efforts with security configuration guidance and software inventories for use with your existing security scanners. The CIS Benchmark for Azure Container Linux (ACL) is now generally available, giving teams a community-developed baseline for assessing node OS security. Its configuration recommendations help platform and security teams identify gaps, prioritize remediation, and conduct consistent reviews without defining assessment criteria from scratch. The latest benchmark can be found here: CIS Azure Linux Benchmarks. Further, Kubernetes users depend on a broad ecosystem of security scanners to assess vulnerabilities. Because ACL nodes do not include an RPM database or a traditional package manager, scanners cannot query installed packages as they would on a general-purpose OS. Instead, each ACL image now includes an embedded software bill of materials (SBOM) in Software Package Data Exchange (SPDX) 2.2 JSON format, listing the components included in the image. Scanners that integrate with this manifest can use the inventory to identify known vulnerabilities. This gives you inspectable evidence of image contents to incorporate into existing security reviews through compatible scanning tools. If you’re a security or vulnerability-scanning provider interested in integrating with ACL’s embedded SBOM manifests, reach out to: AzureLinuxPartners@microsoft.com. Bring immutable infrastructure to your fleet Today’s updates make Azure Container Linux easier to adopt and operate for containerized workloads at scale. Looking ahead, we're exploring support for A/B OS updates to further minimize upgrade disruption, reduce downtime, and simplify rollback scenarios. Stay tuned for future updates as this capability progresses on our roadmap. We’re excited to see what you build on the Azure Container Linux foundation, from established services to emerging agentic workloads. Try ACL in your AKS clusters and let us know what works well and what you'd like to see on our roadmap. Your feedback will help shape what comes next. Get started with deployment guidance and best practices at: aka.ms/azurecontainerlinux. Learn More Azure Container Linux documentation: https://aka.ms/azurecontainerlinux Azure Container Linux on GitHub: https://github.com/microsoft/azure-container-linux Azure Linux product page: https://aka.ms/AzureLinuxProduct Azure Linux documentation: https://aka.ms/azurelinux Joining the ISV partner program: AzureLinuxPartners@microsoft.com
Windows 11 26H2 Windows Search without search highlights??
Hello community support, I just recently finally updated my Win11 Desktop PC to 26H2 from 25H2 and now I noticed that Windows removed the Windows Search >> search highlights (along with the little mini picture in the search box on the taskbar that had a daily highlight) and just now has the boring search history: Current Win 11 version: Edition Windows 11 Home Version 26H2 Installed on 4/6/2025 OS build 26300.9711 Experience Windows Feature Experience Pack 1000.26100.372.0 I also see that the "Show search highlights toggle option no longer exists in Settings>>Privacy & Security>>Search Yes, I can still perform "web searches" but the ready-populated web highlights on the righthand side was a decent feature and now it looks generic and very boring (too simple). Obviously I do not want to mess around with the registry and the "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search" option, but again - why not just keep giving users the control and option to turn highlights on or off rather than force users to not have it at all?? Thanks MJWhich update broke my printer this time?
Which recent Windows update caused my printer to stop working properly, even though it was functioning perfectly before the installation? Now, whenever I try to print documents, the printer either refuses to respond, shows an error message, or remains stuck in the print queue, and I'm wondering whether a faulty driver update or Windows system change is responsible and how I can restore normal printing without reinstalling everything.
