Windows 11 24H2 deployment takes more time
Hi everyone, I was used to spin up a new W11 VM in seconds. With the great improvement of Windows Setup the procedure to apply an OS image takes much longer. What is changed else? Will it fetch and apply an LCU during downlevel / offline setup? not to confuse: the screen looks like IPU, but in fact it is the new UX during baremetal installs.Step-by-Step: How to Setup Copilot Chat in VS Code
Copilot Chat is an AI-powered chatbot leveraging OpenAI's GPT-4, designed to enhance your coding workflow. Learn how to set up Copilot Chat step by step in Visual Studio Code (VS Code). Benefit from personalized and flexible coding environments, code analysis, automated unit test generation, and bug fixes. Prerequisites include an active GitHub account and the latest version of VS Code. Elevate your coding efficiency to new heights with Copilot Chat.
Tips & Tricks on ‘cloning’ Azure SQL virtual machines from captured images
First published on MSDN on Jul 06, 2016 While we have documentation on how to create a VM from captured image under “How to capture a Windows virtual machine in the Resource Manager deployment model”, it doesn’t address some specifics on SQL Server.
Stuck in "Let's finish setting up your PC" screen after latest Update.
After doing a Windows Update today morning my PC gets stuck inside the "Let's finish setting up your PC" screen, without any possibilty for me to interact with it. The Error: After Starting the PC and logging in with my PIN, after the Explorer fully loaded, the Loading screen for the "Let's finish[...]" screen appears. When the loading finishes, it becomes a whitescreen. With alt+tab I can see, that e.g. the Taskmanager opens up when I open it via CTRL+ALT+DEL, but I cannot interact with it since the Setup window cannot be closed, minimized, or interacted with. It looks like this: The "Let's finish[...]" screen does not show up in safe mode, but deactivating the Notification Setting for it (even in Registry) does not fix the Error. I tried uninstalling the latest quality updates, which did not fix the issue. When I try to uninstall the latest functionality updates, I get a Notification that thats not possible and that I should instead reset the PC, which I would like to avoid. Is there any possibilty to get rid of this problem, or should I reset the PC?
Build 26063 fails to install due to setup crash/hang
I am attempting to upgrade from Server Insider 2025 build 26040 to Server Insider 2025 build 26063 Insider Preview Build 26063 is the first ever build that i cannot upgrade to on my server machine. I can't install it because the setup wizard (mounted ISO from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewserver > Setup.exe, even ran as Administrator) fails in either of these 2 ways: - If you choose to search for updates during install (Download updates, drivers, and optional features), it hangs at 2% of "Checking for updates".. forever. It will not proceed, no matter how long you wait. - If you choose not to search for updates ("Not right now"), the setup wizard will crash with code 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN) or 0xC0000005 (Access Violation); it will disappear (close through the crash) immediately after you select "Keep files, settings and apps" for the installation, and proceed with the "Next" button. So at this point, you passed "Checking your PC" and the license terms dialog successfully, but crash at the next step (selecting "Keep files, settings and apps" and clicking Next). What's peculiar about this situation, is that i know it exits in the way of a crash due to it suddenly disappearing along with the above exception codes being thrown in relevant setup logs. However, it doesn't handle as application crash in: Event viewer, or Windows Error Reporting (i even enabled crash dumps for all 3 binaries: setup.exe, SetupPrep.exe, SetupHost.exe .. but no dump file is generated). Therefore, unless you give me some pointers, i can't do much more to provide any diagnostic info for Microsoft to investigate, than logs below.. Here's the Setup Log file contents ( C:\Windows\Logs\MoSetup > BlueBox.log ) of what leads up to the crash, exactly the bits i think, by its timing, are relevant throughout 2 attempts of setup that ended with a crash: 2024-02-27 23:41:34: *******SetupHost Logging End******* 2024-02-27 23:41:34: Process exit code: [0xC0000409] 2024-02-27 23:41:34: LaunchProcessInSession: Error = 0xC0000409 2024-02-27 23:41:34: SetupHost process returned: [0xC0000409], but SetupHostResult registry key was missing. 2024-02-27 23:41:34: LaunchProcessInSession returned: [0xC0000409] 2024-02-27 23:41:34: Checking cleanup registry value... 2024-02-27 23:41:34: Cleanup value missing... assuming no cleanup. 2024-02-27 23:41:34: Skipping cleanup. 2024-02-27 23:41:34: MainHr: Error = 0xC0000409 2024-02-27 23:41:34: wWinMain: Error = 0xC0000409 2024-02-27 23:50:25: BuildInfo: [10.0.26063.1 (ge_release.240216-1326)] 2024-02-27 23:50:25: CommandLine: [D:\Sources\SetupPrep.exe ] 2024-02-27 23:50:25: Opening Box: [D:\Sources\SetupPrep.exe] 2024-02-27 23:50:25: Opening Box Result: [0x0] 2024-02-27 23:50:25: Detecting Product from config file. 2024-02-27 23:50:25: ParseCommandLine: Product from Setup.cfg: [0] 2024-02-27 23:50:25: Deleting box result... 2024-02-27 23:50:25: ScenarioCtrlHelpers::GenerateBoxHash: Calculating file hash... 2024-02-27 23:50:25: ScenarioCtrlHelpers::VerifySetupVersionMatch: Found previously stored file hash. 2024-02-27 23:50:25: ScenarioCtrlHelpers::VerifySetupVersionMatch: Box file hash matches. 2024-02-27 23:50:25: VersionMatch: [Yes] 2024-02-27 23:50:25: StateMatch: Attempting to get Installation Scenario from registry... 2024-02-27 23:50:25: StateMatch: InstallScenario found : 0x1 2024-02-27 23:50:25: StateMatch: Current mode is Install - Attempting to resume... 2024-02-27 23:50:25: Compat Resume Found: [No] 2024-02-27 23:50:25: StateMatch: [No] 2024-02-27 23:50:25: ResumeMode: [No] 2024-02-27 23:50:25: OsUninstallWarning: We are running on Server. No need to warn for Uninstall Allowed. 2024-02-27 23:50:25: OsUninstallWarning: [No] 2024-02-27 23:50:25: Checking cleanup registry value... 2024-02-27 23:50:25: Cleanup value missing... assuming no cleanup. 2024-02-27 23:50:25: Skipping cleanup. 2024-02-27 23:50:25: Cleaning alternate storage paths... 2024-02-27 23:50:25: Cleaning MoSetup Volatile key... 2024-02-27 23:50:25: Removing CorrelationVector registry value... 2024-02-27 23:50:25: Removing cleanup registry value... 2024-02-27 23:50:25: Flushing MoSetup registry key... 2024-02-27 23:50:25: Cleaning working dir... 2024-02-27 23:50:25: Creating path (with ACL): [C:\$WINDOWS.~BT]... 2024-02-27 23:50:25: Creating path: [C:\$WINDOWS.~BT\Sources]... 2024-02-27 23:50:25: ScenarioCtrlHelpers::SetStateInRegistry: Setting Current Scenario: [0x1]... 2024-02-27 23:50:25: ScenarioCtrlHelpers::SetStateInRegistry: Setting Install mode... 2024-02-27 23:50:25: ScenarioCtrlHelpers::GenerateBoxHash: Calculating file hash... 2024-02-27 23:50:25: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] with command-line [/Install /Media /InstallFile "D:\Sources\Install.wim" /MediaPath "D:"] in Session: [-1] 2024-02-27 23:50:25: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] [/Install /Media /InstallFile "D:\Sources\Install.wim" /MediaPath "D:"] from []! 2024-02-27 23:50:25: Waiting for process events... 2024-02-27 23:51:08: *******SetupHost Logging Begin******* 2024-02-27 23:51:08: *******SetupHost Logging End******* 2024-02-27 23:51:08: Process exit code: [0xC0000005] 2024-02-27 23:51:08: LaunchProcessInSession: Error = 0xC0000005 2024-02-27 23:51:08: SetupHost process returned: [0xC0000005], but SetupHostResult registry key was missing. 2024-02-27 23:51:08: LaunchProcessInSession returned: [0xC0000005] 2024-02-27 23:51:08: Checking cleanup registry value... 2024-02-27 23:51:08: Cleanup value missing... assuming no cleanup. 2024-02-27 23:51:08: Skipping cleanup. 2024-02-27 23:51:08: MainHr: Error = 0xC0000005 2024-02-27 23:51:08: wWinMain: Error = 0xC0000005 Log contents that are written up to a moment that setup is still hung at 2%, in case of fail type number 1 (when i select to search updates): 2024-02-27 23:56:03: BuildInfo: [10.0.26063.1 (ge_release.240216-1326)] 2024-02-27 23:56:03: CommandLine: [D:\Sources\SetupPrep.exe ] 2024-02-27 23:56:03: Opening Box: [D:\Sources\SetupPrep.exe] 2024-02-27 23:56:03: Opening Box Result: [0x0] 2024-02-27 23:56:03: Detecting Product from config file. 2024-02-27 23:56:03: ParseCommandLine: Product from Setup.cfg: [0] 2024-02-27 23:56:03: Deleting box result... 2024-02-27 23:56:03: ScenarioCtrlHelpers::GenerateBoxHash: Calculating file hash... 2024-02-27 23:56:03: ScenarioCtrlHelpers::VerifySetupVersionMatch: Found previously stored file hash. 2024-02-27 23:56:03: ScenarioCtrlHelpers::VerifySetupVersionMatch: Box file hash matches. 2024-02-27 23:56:03: VersionMatch: [Yes] 2024-02-27 23:56:03: StateMatch: Attempting to get Installation Scenario from registry... 2024-02-27 23:56:03: StateMatch: InstallScenario found : 0x1 2024-02-27 23:56:03: StateMatch: Current mode is Install - Attempting to resume... 2024-02-27 23:56:03: Compat Resume Found: [No] 2024-02-27 23:56:03: StateMatch: [No] 2024-02-27 23:56:03: ResumeMode: [No] 2024-02-27 23:56:03: OsUninstallWarning: We are running on Server. No need to warn for Uninstall Allowed. 2024-02-27 23:56:03: OsUninstallWarning: [No] 2024-02-27 23:56:03: Checking cleanup registry value... 2024-02-27 23:56:03: Cleanup value missing... assuming no cleanup. 2024-02-27 23:56:03: Skipping cleanup. 2024-02-27 23:56:03: Preserve working path: [No] 2024-02-27 23:56:03: Cleaning alternate storage paths... 2024-02-27 23:56:03: Cleaning MoSetup Volatile key... 2024-02-27 23:56:03: Removing CorrelationVector registry value... 2024-02-27 23:56:03: Removing cleanup registry value... 2024-02-27 23:56:03: Flushing MoSetup registry key... 2024-02-27 23:56:03: Cleaning working dir... 2024-02-27 23:56:03: Attempting to preserve existing logs... 2024-02-27 23:56:03: Creating path: [C:\WINDOWS\Panther\NewOs\Panther]... 2024-02-27 23:56:03: Copying [C:\$WINDOWS.~BT\Sources\Panther] -> [C:\WINDOWS\Panther\NewOs\Panther]... 2024-02-27 23:56:03: Attempting to clean installation drive at [C]... 2024-02-27 23:56:03: Acquiring privileges... 2024-02-27 23:56:03, Info SPCleanupInstallationDrive: Cleaning up C:\ 2024-02-27 23:56:03, Info Active tracing sessions: 2024-02-27 23:56:03, Info Session name: Eventlog-Security 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x188001c0 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: CimFSUnionFS-Filter 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\system32\Logfiles\WMI\CimFSUnionFS-Filter.etl 2024-02-27 23:56:03, Info Log file mode: 0x00800000 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: DiagLog 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x10800180 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: Diagtrack-Listener 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\System32\LogFiles\WMI\Diagtrack-Listener.etl.005 2024-02-27 23:56:03, Info Log file mode: 0x08800011 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: EventLog-Application 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x19800180 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: EventLog-System 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x98800180 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: FilterMgr-Logger 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x10808400 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace 2024-02-27 23:56:03, Info Log file name: C:\Windows\System32\drivers\DriverData\LogFiles\WMI\Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace.etl 2024-02-27 23:56:03, Info Log file mode: 0x80800002 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: NtfsLog 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\system32\Logfiles\WMI\NtfsLog.etl.001 2024-02-27 23:56:03, Info Log file mode: 0x00800000 2024-02-27 23:56:03, Info Flush timer: 15 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: ReFSLog 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\system32\Logfiles\WMI\ReFSLog.etl 2024-02-27 23:56:03, Info Log file mode: 0x00800000 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: UAL_Usermode_Provider 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x00800100 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: UBPM 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x108001d0 2024-02-27 23:56:03, Info Flush timer: 20 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: WdiContextLog 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\System32\WDI\LogFiles\WdiContextLog.etl.003 2024-02-27 23:56:03, Info Log file mode: 0x00800082 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: LSA 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\system32\LogFiles\LSA\LSA.etl 2024-02-27 23:56:03, Info Log file mode: 0x10800002 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: CldFltLog 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\System32\LogFiles\CloudFiles\CldFlt1.etl 2024-02-27 23:56:03, Info Log file mode: 0x90800002 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: MpWppTracing-20240227-235345-00000003-ffffffff 2024-02-27 23:56:03, Info Log file name: C:\ProgramData\Microsoft\Windows Defender\Support\MpWppTracing-20240227-235345-00000003-ffffffff.bin 2024-02-27 23:56:03, Info Log file mode: 0x00800002 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: WindowsUpdate_trace_log 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\Logs\WindowsUpdate\WindowsUpdate.20240227.234336.528.1.etl 2024-02-27 23:56:03, Info Log file mode: 0x11802009 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: SP_DOWNLEVEL_TELEMETRY_ETW_SESSION 2024-02-27 23:56:03, Info Log file name: C:\WINDOWS\Panther\DlTel.etl 2024-02-27 23:56:03, Info Log file mode: 0x01400001 2024-02-27 23:56:03, Info Flush timer: 0 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Session name: UAL_Kernelmode_Provider 2024-02-27 23:56:03, Info Log file name: 2024-02-27 23:56:03, Info Log file mode: 0x00800100 2024-02-27 23:56:03, Info Flush timer: 1 2024-02-27 23:56:03, Info Enable flags: 0x00000000 2024-02-27 23:56:03, Info Found relevant tracing session: name=[SP_DOWNLEVEL_TELEMETRY_ETW_SESSION], logfilename=[c:\windows\panther\dltel.etl] 2024-02-27 23:56:03, Info Filter WinSetupMon not installed; nothing to unload 2024-02-27 23:56:03, Info SPCleanupInstallationDrive: Not suspended data in registry keys, no need for cleanup 2024-02-27 23:56:03, Info DeletePath: Attempting to obliterate [C:\$WINDOWS.~BT] (final path [\\?\Volume{a3b54d96-0000-0000-0000-100000000000}\$WINDOWS.~BT]). 2024-02-27 23:56:03: Creating path (with ACL): [C:\$WINDOWS.~BT]... 2024-02-27 23:56:03: Creating path: [C:\$WINDOWS.~BT\Sources]... 2024-02-27 23:56:03: ScenarioCtrlHelpers::SetStateInRegistry: Setting Current Scenario: [0x1]... 2024-02-27 23:56:03: ScenarioCtrlHelpers::SetStateInRegistry: Setting Install mode... 2024-02-27 23:56:03: ScenarioCtrlHelpers::GenerateBoxHash: Calculating file hash... 2024-02-27 23:56:03: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] with command-line [/Install /Media /InstallFile "D:\Sources\Install.wim" /MediaPath "D:"] in Session: [-1] 2024-02-27 23:56:03: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] [/Install /Media /InstallFile "D:\Sources\Install.wim" /MediaPath "D:"] from []! 2024-02-27 23:56:03: Waiting for process events... I hope that i can continue updating my machine, starting from the next Windows Server insider preview build. I am certain nothing changed on my end since the last successful upgrade(s), so i am confident this is a Microsoft regression, which seems logical as it's known the latest couple builds overhauled the Setup experience. So, please let me know if anyone else encountered this, or if MS will investigate. cc Brentfor and Elden_Christensen
