user verification Archives

AppWizard

April 10, 2026

Kazakhstan Considers National Messaging App Aitu for Insurance Companies – The Times Of Central Asia

Kazakhstan’s Agency for Regulation and Development of the Financial Market is considering the domestic messaging platform Aitu for communication between insurance companies, non-bank financial institutions, and their clients. The regulator has encouraged market participants to assess Aitu as a communication tool aimed at enhancing personal data protection. Concerns have been raised about Aitu’s user base, functionality, integration costs, and the absence of clear regulatory guidelines for handling personal and financial data. The adoption of Aitu is not mandatory but is seen as a potential secure communication channel. Aitu’s infrastructure supports high data protection due to localized servers in Kazakhstan, which reduces risks of cross-border data issues. The platform features end-to-end encryption and biometric identification through Aitu Passport, aiming to enhance user verification and minimize phishing and identity theft risks. The agency noted that open APIs and business dashboards could allow financial institutions to integrate with Aitu cost-effectively. Additionally, government agencies and quasi-state companies have been encouraged to use Aitu for official communications.

Winsage

November 27, 2025

Microsoft Security Keys May Require PIN After Recent Windows Updates

Microsoft announced an update for FIDO2 security keys on Windows 11, introducing a new prompt for users to set up a PIN during authentication. The rollout began with preview update KB5065789 on September 29, 2025, for OS Builds 26200.6725 and 26100.6725, and was completed with security update KB5068861 on November 11, 2025, for OS Builds 26200.7171 and 26100.7171. This update affects sign-ins where a Relying Party (RP) or Identity Provider (IDP) requests User Verification set to “Preferred” for keys without a PIN, in accordance with WebAuthn specifications. Users must now set up a PIN during authentication flows, not just during registration. To avoid PIN prompts, RPs or IDPs can set “userVerification” to “discouraged.” There is no option to roll back the changes.

Winsage

November 27, 2025

Microsoft Security Keys May Require a PIN After Recent Windows Updates

Microsoft has updated Windows to require users to create and configure a PIN for FIDO2 security keys during sign-in, even if they did not set one during initial registration. This requirement applies to users who install the Windows preview update released on September 29, 2025 (KB5065789, OS Builds 26200.6725 and 26100.6725) or later updates. The necessity for a PIN is triggered when a Relying Party (RP) or Identity Provider (IDP) requests User Verification set to “Preferred.” The update aims to ensure compliance with WebAuthn specifications and began rolling out gradually on Windows 11 devices after the September 29, 2025 update, with full deployment completed by the November 11, 2025 security update (KB5068861, OS Builds 26200.7171 and 26100.7171). Windows now supports three verification settings: Discouraged, Preferred, and Required, with “Preferred” indicating that user verification should occur if supported by the authenticator.

Winsage

November 26, 2025

Microsoft: Security keys may prompt for PIN after recent updates

Microsoft issued a notice to users about a new behavior related to FIDO2 security keys following Windows updates since the September 2025 preview update. This change affects devices on Windows 11 versions 24H2 or 25H2, where users may be prompted to enter a PIN during authentication. The adjustment aligns with WebAuthn specifications, which outline protocols for authentication methods, including PINs and biometrics. User verification can be categorized as discouraged, preferred, or required, with "preferred" necessitating a PIN setup if supported by the authenticator. The rollout began after the KB5065789 preview update and was completed with the November KB5068861 security update. Microsoft stated that after installing the September 29, 2025 update, users might need to create a PIN to sign in with a security key, even if it was not required during initial registration. This behavior occurs when a Relying Party or Identity Provider requests User Verification = Preferred during authentication with a FIDO2 security key lacking a PIN. Organizations can opt to adjust the user verification setting to "discouraged" if they do not want to require users to create or enter PINs. FIDO2 security keys enable passwordless authentication by requiring the physical presence of a USB, NFC, or Bluetooth token, gaining popularity as organizations seek to reduce risks associated with traditional passwords.

TrendTechie

November 26, 2025

Официальный сайт Xubuntu был взломан — вместо торрента распространялся вредоносный файл для Windows

Recent advancements in user verification technology have introduced innovative methods to confirm user identity, enhancing security and user experience. One notable implementation is a visually engaging captcha system that combines graphical elements and interactive features, prompting users to confirm their humanity through simple actions. This system may include captivating SVG graphics requiring user interaction, such as checking a box, accompanied by messages like "Please verify you are a human." Additionally, developers are exploring machine learning algorithms to analyze user behavior patterns for better differentiation between human users and bots, reducing false positives and improving security without hindering legitimate users.

Winsage

August 15, 2025

Microsoft patches more than 100 Windows security flaws – update your PC now

Microsoft's August Patch Tuesday update addresses 107 vulnerabilities in Windows, including 13 critical ones. It affects all current versions of Windows, including Windows 10, Windows 11, and Windows Server. The update fixes security issues in components like File Explorer, Remote Desktop, and Hyper-V, as well as bugs in Microsoft Office, Edge, and Teams. Nine critical vulnerabilities involve remote code execution. One vulnerability, CVE-2025-53779, is a zero-day flaw in the Windows Kerberos authentication system that could grant domain administrator privileges if exploited. The update also introduces new features, including a revamped error screen called the Black Screen of Death and Quick Machine Recovery for troubleshooting boot failures. Users can check for the update in the Windows Update section of Settings.

Winsage

July 2, 2025

You can use 1Password passkeys directly in Windows 11 soon

Microsoft is testing a deeper integration of 1Password’s passkey feature within Windows 11, marking a shift towards a passwordless future. Passkeys enhance security by combining possession (like a smartphone) and biometric identifiers (like face or fingerprint). To enable the integration, users must install the 1Password Beta and navigate to Settings > Passkeys > Advanced options, requiring verification through Windows Hello. This feature is currently available in the Windows 11 Insider Preview Build 26200.5670 (KB5060838) within the Dev Channel.

Winsage

June 28, 2025

Announcing Windows 11 Insider Preview Build 26120.4520 (Beta Channel)

Windows 11 Insider Preview Build 26120.4520 (KB5060834) has been released to the Beta Channel for users on Windows 11, version 24H2. This update includes new features, improvements, and fixes, which are being gradually rolled out. New features include: - A passwordless improvement in collaboration with 1Password, allowing users to integrate a plugin passkey provider and authenticate using Windows Hello. - Temporary disabling of Japanese support in voice access due to bugs. - Changes to default browser settings, where the new default browser will be pinned to the Taskbar and Start menu unless opted out. Fixes include: - Resolved crashes in File Explorer Home and issues with thumbnail visibility. - Addressed duplicate entries in the Start menu and animation issues with folder expansion. - Fixed a crash involving ctfmon.exe and resolved a memory leak related to the lock screen slideshow. - Improved responsiveness of system dialogs to text scaling. Known issues include: - New Beta Channel joiners may experience a rollback issue during installation. - Touch navigation in the Start menu may not function reliably, and drag-and-drop capabilities are limited. - Xbox Controller users may encounter bugchecks via Bluetooth. - Narrator scan mode may not function correctly in File Explorer for AI actions. - Limitations in pinning within the new widgets board experience. Windows Insiders in the Beta Channel will receive updates based on Windows 11, version 24H2 via an enablement package, with features rolled out using Controlled Feature Rollout technology. Some features may not be publicly released and could change based on feedback.

Winsage

June 27, 2025

Announcing Windows 11 Insider Preview Build 26200.5670 (Dev Channel)

Windows 11 Insider Preview Build 26200.5670 (KB5060838) has been released to the Dev Channel. Key updates include: - Passwordless Improvements: Integration with 1Password for passkey management, allowing users to sign in using Windows Hello after enabling the plugin credential manager. - Versioning Update: The build updates the versioning to 25H2, marking it as this year's annual feature update. - Voice Access: Support for Japanese is temporarily disabled due to bugs. - Settings Update: The new default browser will be pinned to the Taskbar and Start menu unless opted out. - File Explorer Fixes: Issues causing crashes and thumbnail disappearances have been resolved. - Start Menu Fixes: Duplicate entries and animation inconsistencies have been corrected. - Input Fixes: A significant crash affecting typing capabilities has been addressed. - General Fixes: Resolved an issue with the boot sound and fixed a memory leak related to the lock screen slideshow. - Known Issues: Users may experience rollback errors during updates, touch navigation issues in the Start menu, and bugs with Xbox Controllers via Bluetooth. - Reminders: Updates are rolled out gradually, and features may evolve or be removed based on feedback.

Winsage

April 15, 2025

Windows Server 2025 may lose DC connectivity after restart

Microsoft has warned about potential accessibility issues with Windows Server 2025 domain controllers after a restart, where affected servers revert to the default firewall profile, disrupting applications and services. A temporary workaround involves manually restarting the network adapter on the impacted servers using the PowerShell command: Restart-NetAdapter *. This workaround needs to be reapplied after each restart of the domain controller, and Microsoft recommends setting up a scheduled task to automate this process. Windows Server 2025, launched earlier this year, introduced new features and security enhancements but has faced previous issues, including freezing Remote Desktop sessions and accidental upgrades from Windows Server 2022. Developers are currently working on a permanent solution for the domain controller issue.