Forum Widgets
Latest Discussions
Building and Deploying a Kiosk Platform with WinUI 3 and Windows Pro
Hello, Over the last few months I have been working on a kiosk platform built with WinUI 3, Assigned Access and Windows Pro. The project goes well beyond the application itself and includes deployment, configuration, system lockdown, policy management, rollback and long-term maintainability. One of the most interesting lessons learned was that managing a kiosk is often less about the application and more about managing Windows itself: power settings, updates, lock screen, privacy settings, touch keyboard, user experience restrictions and system recovery. One challenge that isn't immediately obvious from the documentation is how to build, package, deploy and maintain a modern WinUI 3 desktop application within an Assigned Access environment on Windows Pro. At first glance, Assigned Access appears to solve most kiosk requirements. In practice, deploying and operating a modern desktop application in a production environment requires addressing many additional challenges that fall outside the scope of Assigned Access itself. Assigned Access itself is well documented, but most examples and tutorials focus on Microsoft Edge, UWP applications or predefined kiosk scenarios. Building, packaging, deploying and maintaining a WinUI 3 application in a real-world kiosk environment introduces additional challenges that are not always immediately apparent when approaching the platform for the first time. This was one of the reasons why the project evolved beyond application development and became an exercise in Windows deployment, configuration management and operational maintainability. Another interesting aspect of the project was that it wasn't a greenfield implementation. The platform originally relied on a UWP-based kiosk application running on Windows 10. One of the objectives was to modernize the solution by moving to WinUI 3 while preserving the existing deployment model and remaining compatible with Windows 10 environments. This migration raised several practical questions around application packaging, deployment, kiosk integration and operational management, well beyond the user interface itself. To address these challenges, I designed a policy-based approach where system settings are handled through a three-step process: → Save the original state → Apply the required configuration → Restore the original state instead of the more traditional approach: → Apply a configuration → Remove the configuration This made the solution significantly more reversible, predictable and maintainable. I believe the lessons learned from this migration and deployment effort could be useful to other developers and architects working on kiosk solutions based on Windows Pro, Assigned Access and WinUI 3. I would like to share this experience as a technical article for the Windows Community Hub. Is there a recommended process for community members who would like to contribute a technical article or case study? Thank you. Bets Regards Diego Marino Monetti
Factory Reset Windows 10 without user intervention
I've looked for this answer online and have come across the "systemreset -factoryreset" command which works, but it comes up with the prompt asking if I want to keep my files or remove everything, I want to remove everything, but without the prompt. We are not doing this from any pre-exiting images, and our laptops are running the pre-loaded Windows 10 Pro install, we are just using the in-built Windows 10 "reset this PC" feature as we have no MDM configured. We just want the laptops to be totally reset so they don't contain any company information, we're not bothered about completing the OOBE once they are wiped. We are trying to accomplish this remotely as our users are all at home, so I need to automate it and have no user involvement in the process, I just want it to factory reset, and bring the laptop up to the off-the-shelf state configuration. We have the facility to push commands and scripts to the laptops so was hoping to do this via powershell. Does anyone know if this is possible? ThanksBitLocker Loop / Soft-Brick After Secure Boot 2023 Certificate Update (ASUS ROG G713QE)
Hello, following the June 2026 Windows Update regarding the transition to "Microsoft UEFI CA 2023" Secure Boot keys, my machine (ASUS ROG Strix G713QE, AMD Ryzen CPU with fTPM) experienced a critical failure cascade leading to an infinite BitLocker recovery loop. Exact Step-by-Step Failure Chronology: Initial Post-Update Boot: The machine booted directly into the blue BitLocker Recovery screen, prompting for the 48-digit recovery key. First Unlock & WinRE Access: Entering the correct 48-digit key successfully decrypted the drive and allowed access to the Windows Recovery Environment (WinRE). Standard Recovery Failures: All default automated repair methods (Startup Repair, etc.) failed, systematically looping back to the WinRE menu. Failed Update Uninstall: Attempting to use the "Uninstall latest quality/feature update" option threw an error stating that Windows could not uninstall the update due to an update currently in progress. (Note: This strongly suggests that pending transaction flags or file-lock attributes in the Component-Based Servicing store were never cleared due to the unfinalized update state). System Restore Attempt: A System Restore point was selected. The progress bar completed successfully, and the validation/success pop-up appeared. A reboot was then triggered. The Hard Loop: Upon this post-restore reboot, the system fell into an infinite BitLocker loop. Entering the 48-digit key now causes an immediate crash/reset, completely locking out any further access to the Windows Recovery Environment (WinRE). Current Root Cause Analysis: The only way to regain temporary access to the OS was to perform a full UEFI BIOS reflash, which allowed exactly one functional boot (rebooting at this state threw us back to the BitLocker hard loop). Once inside, the loop was permanently stabilized by executing the following command in an elevated prompt to purge the stuck transaction: DISM /Online /Cleanup-Image /RevertPendingActions BitLocker protection has also been suspended (manage-bde -protectors -disable C:) to prevent the TPM from locking up the system again. There is a major structural conflict on this motherboard generation between the new Microsoft CA 2023 certificate write-orders in the NVRAM, the CBS transaction state, and the ASUS fTPM firmware validation. Please deploy a BIOS fix or implement a compatibility safeguard hold on Windows Update for this hardware profile.WDS: PXE-Boot a client with CA2023 certificate and CA2011 revoked
Hi Microsoft, we try to PXE-Boot Notebooks that have SecureBoot enabled and have the CA2023 certificates. Furthermore the Clients have CA2011 Certificates revoked. Our Environment / Setup: WDS-Server: Fresh installed Windows Server 2025 (24H2) with latest cumulative Update (2026-05). WDS-Serverrole enabled. WDS configured and boot-image attached When booting a client with SecureBoot disabled, booting works. But when SecureBoot is enabled we get the shown message: When having a look at the files in the WDS Folder c:\RemoteInstall\boot\x64 I can see that there are still the EFi-Files signed with the old 2011 CA... So it is necessary to have EFI-Files (especially for WDS!) which are signed with CA 2023. I already tried to use wdsmgfw.efi and bootmgfw.efi Files from a winpe.wim from a Win 11 ADK 2025, but then I get errors like "0xc0000704". Disabling SecureBoot works, but is just a workaround. We need a fix for that Issue....
How do I transfer Windows 10 setup to new 11pc under a different MS account?
I bought a new Windows 11 pc, and am trying to set it up based on my old Windows 10 pc. I manually ran the Windows Backup to make sure all is OK, and that is when I found out that my old pc ... is logged into Windows with an outlook email, but MS365/OneDrive (365/OD) is logged into with a hotmail email (i.e. two different accounts). Hence, the Windows backup only includes the pc/Windows setup (other apps and their config, desktop layout, credentials, etc.), while the 365/OD account has all of the folders/files/data (which is always backed up too). I want to consolidate everything on the new pc to the hotmail account (which already has 365/OD), but Microsoft does not allow the Windows backup to go from one account to another. Is there any way to transfer the old Window 10 pc settings (other apps and their config, desktop layout, other settings, etc.), basically everything in the Windows Backup except the folders/files, to the new Windows 11 pc with a different MS account? (the hotmail account already has MS365/OneDrive, so I just need the rest of the Windows Backup)
Installing Windows server 2025 is failing with this error.
when booted from Winpe and triggered installation of Windows server 2025 OS install it is failing. Can anyone helps with this. below is the error. 2026-02-18 14:10:04, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:10:04, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::GetSettingsParameters(205): Result = 0x8000000A[gle=0x000036b0] 2026-02-18 14:10:04, Error MOUPG CSetupManager::GetWuIdFromRegistry(12357): Result = 0x80070002 2026-02-18 14:10:05, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:10:05, Error MOUPG CDlpActionLanguageSelection::GetInternationalSettingsFromUnattend(356): Result = 0x8007000D 2026-02-18 14:10:17, Error MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(3611): Result = 0x80070490 2026-02-18 14:10:17, Error MOUPG ProductKey: Failed to report Host OS channel to telemetry. 2026-02-18 14:10:24, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:10:25, Error CONX aepic: ERROR,GetPrivacyLevel,81,GetActivationFactory [0x80040154] 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::IsMeteredConnection,29,Failed to get NetworkCostType assuming metered network [0x80040154]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::GetSettingsFromEndpoint,244,Failed to retrieve Sqm DeviceId: [0x80070002]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::GetSettings,94,Failed to get settings from endpoint [0x80070002]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,ProcessJson,606,Unable to GetSettings [0x80070002] 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::IsMeteredConnection,29,Failed to get NetworkCostType assuming metered network [0x80040154]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::GetSettingsFromEndpoint,244,Failed to retrieve Sqm DeviceId: [0x80070002]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::GetSettings,94,Failed to get settings from endpoint [0x80070002]. 2026-02-18 14:10:25, Error CONX hwreqchk: ERROR,ProcessJson,606,Unable to GetSettings [0x80070002] 2026-02-18 14:10:30, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:10:31, Error MOUPG CDlpResponseInstallLocation::ObtainData(122): Result = 0x8007000D 2026-02-18 14:10:31, Error MOUPG CDlpActionDiskManagement::GetDriveLetterFromUnattend(877): Result = 0x8007000D 2026-02-18 14:12:40, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:12:40, Error CDiagnosticsHelper::PersistDiagnosticsData: Failed to persist diagnostics data.: Win32Exception: \\?\E:\$WINDOWS.~BT\Sources\Diagnostics: Access is denied. [0x00000005] class UnBCL::DirectoryInfo *__cdecl UnBCL::Directory::CreateDir(const class UnBCL::String *)[gle=0x00000005] 2026-02-18 14:12:46, Error SP CNewSystem::PreInitialize: FveCheckSuspendBitLockerOnUpgrade failed: 0x8031004a, assuming auto-unlock is not supported 2026-02-18 14:15:51, Error SP Sysprep specialize offline failed. Error: 0xC06D007E[gle=0x0000007a] 2026-02-18 14:15:51, Error SP Operation failed: Run sysprep specialization offline on C:\$WINDOWS.~BT\NewOS. Error: 0xC06D007E 2026-02-18 14:15:51, Error SP COperationQueue::Sort: Could not find an execution phase for 123[gle=0x00000002] 2026-02-18 14:15:51, Error SP ExecuteOperations: Operations cannot be sorted. This is a fatal failure.[gle=0x00000002] 2026-02-18 14:15:51, Error SP ExecuteOperations: Main operation execution failed. Error: 0x8007000D 2026-02-18 14:15:51, Error SP ExecuteOperations: Failed execution phase Pre-Finalize. Error: 0x8007000D 2026-02-18 14:15:51, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure![gle=0x0000000d] 2026-02-18 14:15:51, Error MOUPG MoSetupPlatform: Using action error code: [0xC06D007E][gle=0x0000000d] 2026-02-18 14:15:51, Error MOUPG CDlpActionPreFinalize::ExecuteRoutine(784): Result = 0xC06D007E[gle=0x0000000d] 2026-02-18 14:15:51, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(503): Result = 0xC06D007E 2026-02-18 14:15:51, Error MOUPG CDlpTask::ExecuteAction(3334): Result = 0xC06D007E 2026-02-18 14:15:51, Error MOUPG CDlpTask::ExecuteActions(3487): Result = 0xC06D007E 2026-02-18 14:15:51, Error MOUPG CDlpTask::Execute(1643): Result = 0xC06D007E 2026-02-18 14:15:51, Error MOUPG CSetupManager::ExecuteTask(3116): Result = 0xC06D007E[gle=0x00003b01] 2026-02-18 14:15:51, Error MOUPG CSetupManager::ExecuteTask(3078): Result = 0xC06D007E[gle=0x00003b01] 2026-02-18 14:15:51, Error MOUPG CSetupManager::ExecuteInstallMode(1159): Result = 0xC06D007E[gle=0x00003b01] 2026-02-18 14:15:51, Error MOUPG CSetupManager::ExecuteDownlevelMode(609): Result = 0xC06D007E[gle=0x00003b01] 2026-02-18 14:15:51, Error MOUPG CSetupManager::GetDUSetupResults(8418): Result = 0x80070490 2026-02-18 14:16:08, Error MOUPG CSetupManager::Execute(345): Result = 0xC06D007E[gle=0x0000007f] 2026-02-18 14:16:08, Error MOUPG CSetupHost::Execute(517): Result = 0xC06D007E[gle=0x0000007f]Download for storahci.inf
I am using imaging/deployment software that is trying to do something smart with drivers so that deploying to different models of computers works. It needs the storage and chipset .inf files during the deploy process. Apparently the storage driver I need is storahci.inf which is a Windows built-in driver. I've heard to look in C:\Windows\System32\DriverStore\FileRepository. I do see the following files in that location but not storahci.inf. storfwupdate.inf_amd64_47e7389d7a7fd4b9 stornvme.inf_amd64_cecd5bc5a5bbbce1 storufs.inf_amd64_cf64753adecb48b7 The .sys file is not accepted by the deployment software. Is the storahci.inf file available somewhere (from an official source)?
Windows 11 and Microsoft 365 deployment lab kit - Licenses expire in 2 days
Hello: The licenses for the server OS's in the lab (linked below) expire in 2 days, despite what the documentation says. Please update it. The email address in the doc does not exist. https://learn.microsoft.com/en-us/microsoft-365/enterprise/modern-desktop-deployment-and-management-lab?view=o365-worldwide%20licensing%20expired%20and%20is%20unusable. Thank you.
Win7 x64: KB4534310 fails with "not applicable" despite all prerequisites met
Hello everyone, I'm facing a persistent issue trying to install update KB4534310 on a *Windows 7 Professional SP1 (x64)* system. Despite thorough preparation, the installer fails with "This update is not applicable to your computer." *System Configuration:* - *OS:* Windows 7 Professional Service Pack 1, build 7601 - *Architecture:* x64 - *Language:* Russian - *Registry data:* EditionID=Professional, InstallationType=Client *Prerequisites installed (in order):* 1. ✅ KB4490628 (Servicing Stack Update) 2. ✅ KB4474419 (SHA-2 Update) 3. ✅ KB4536952 (Service Stack Update) *Diagnostics & repairs performed:* - *Windows Update components reset:* Stopped services (wuauserv, cryptSvc, bits, msiserver), renamed SoftwareDistribution and catroot2 folders, restarted services. - *System file check:* sfc /scannow completed successfully - no integrity violations found. - *Registry check:* EditionID, ProductName, InstallationType all show correct values. - *Service status:* All relevant services are running properly. *The Problem:* After all preparations, the KB4534310 installer (downloaded both via Windows Update and manually from Microsoft Update Catalog) consistently gives error: *"This update is not applicable to your computer."* *Notable observation:* The C:\Windows\Logs\WindowsUpdate folder is missing on the system, even after completely resetting Windows Update components. I would greatly appreciate any help in identifying the root cause. Are there any additional logs or diagnostic tools that could pinpoint the issue? Has anyone encountered a similar situation? Thank you in advance for any suggestions!
