in-place upgrade fails from b29574 to latest vnext b29595
Hi all, is anyone facing the same issue IPU fails on a fresh b29574 upgrading to latest using WU? provided more information in feedback hub. Thanks for sharing your experience. as a next attempt I will mount ISO and upgrade. mind b29574 was the base bare metal installation so no previous IPUs involved. related feedback https://aka.ms/AA11g03n Installed roles: - Hyper-V Specialities: tried SysWOW64 removal but failed to do so https://aka.ms/AA11eyy5 OS Drive is ReFS, potientially related https://aka.ms/AA11eyy8 <?xml version="1.0" encoding="utf-16"?> <SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag"> <Version>1.7.0.0</Version> <ProfileName>FindRollbackFailure</ProfileName> <ProfileGuid>3A43C9B5-05B3-4F7C-A955-88F991BB5A48</ProfileGuid> <FailureData>0xc1900101-0x20017 Error: SetupDiag reports rollback failure found.Last Phase = FinalizeLast Operation = Cleanup external drivers after installationError = 0xC1900101-0x20017</FailureData> <FailureData>LogEntry: </FailureData> <FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData> <FailureDetails>RollbackErrorCode = 0xC1900101, ExtendedCode = 0x20017, LastOperation = Cleanup external drivers after installation, LastPhase = Finalize</FailureDetails> <Setup360Result>0xc1900101</Setup360Result> <Setup360Extended>0x20017</Setup360Extended> <SetupPhaseInfo> <PhaseName>Finalize</PhaseName> <PhaseStartTime>06/06/2026 13:16:53</PhaseStartTime> <PhaseEndTime>06/06/2026 13:17:35</PhaseEndTime> <PhaseTimeDelta>0:00:00:42.0000000</PhaseTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupPhaseInfo> <SetupOperationInfo> <OperationName>Cleanup external drivers after installation</OperationName> <OperationStartTime>06/06/2026 13:17:35</OperationStartTime> <OperationEndTime>06/06/2026 13:17:35</OperationEndTime> <OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupOperationInfo> </SetupDiag> also noticing uncommon links in root as if I were using FAT32.Server flighting not being offered on 29595 on 3 VMs
Hi, I'm on not getting build 29602 offered as a flight through Windows update on any of my VMs and I can figure out why, it has not been offered in the last couple of builds. Is anyone else experiencing this or have any ideas of how to fix this? Optional diagnostics are on and they are connected to my account under insider setting in Windows update settings. I am just not getting offered the build flight. Thanks Kevin
Windows Server vNext cannot be activated
Error Code 0xC004F012 when trying to activate WS vNext Datacenter with Key 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67. vbscript is removed, implying the future removal of this component from the OS. It appear that Windows Activation still relying on vbscript. Is this something that is on the roadmap? Would wish for native PowerShell support / module instead of vbscript.
Automate Copilot in Excel
Hi, Is it possible to automate opening Copilot in Excel and send a prompt using VBA? Currently, Copilot in excel seems to work only through the UI, where we have to manually click the Copilot button in the ribbon section and paste the prompt. I want to automate this process so that, with a single click, Excel opens Copilot and enters the prompt automatically. If this is not possible, are there any alternative approaches to achieve similar automation?
Copilot Excel error "Failed to fetch document context" - Cannot use paid service
Environment: Microsoft 365 (paid subscription, recently upgraded) Excel for Windows (desktop app) Copilot in Excel Issue: I am repeatedly receiving the error message "Failed to fetch document context due to an internal error" when trying to use Copilot in Excel. This error has been occurring for multiple days across multiple sessions. What happens: I open my Excel workbook (.xlsx file) I open Copilot from the ribbon I ask Copilot to perform a task (e.g., write data to cells, read from a table) Copilot responds as if it completed the task Nothing actually happens in my workbook — no data is written, no changes are made The error "Failed to fetch document context due to an internal error" appears What I've tried: Restarting Excel (multiple times) Closing and reopening Copilot panel Signing out and signing back in to my Microsoft account Checking for updates Waiting several hours/days and trying again Force-closing Excel via Task Manager Starting fresh chat sessions Contacted Microsoft Support chat (they directed me here) None of these resolved the issue. Impact: I recently upgraded to a paid subscription specifically to use Copilot I cannot use the service I paid for Simple tasks like writing text values to cells do not work Copilot claims tasks are "done" but nothing actually changes in my workbook This has been happening for 5+ days Questions: Is this a known server-side issue? Is there a fix or workaround? How can I get this resolved or request a refund for a non-functional service? Thank you for any help!Cloud PC Display Name Vs. Computer Name
I have seen a bit of confusion between Windows 365 Cloud PC Display Name Vs. Computer Name. I thought to create a quick discussion thread on this topic so that it can help the IT Community if there is any confusion at all. I have noticed different methods to change the Display names of Cloud PCs. Both the end-users and admins can change the display name of the Cloud PC. Even there are Graph API options to perform this action. The following is the Display Name of the Windows 365 Cloud PC, and end-users (w365 client portal) and admins can change this. This display name won't appear in any management tools such as Azure AD, Active Directory, Intune, SCCM, etc. (if I'm not wrong). The Windows 365 Business admin portal allows you to change the Display Name of the Cloud PC from the admin side. The Windows 365 Cloud PC computer name is another property that is part of the core operating system, such as Windows 10 or Windows 11. The computer name is a device property that Azure AD, MEM Intune, and third-party applications use as one of the primary identifiers of a Windows device. You can use the standard "Windows" methods to change the computer name of the Cloud PC, but I don't think this is supported for the Cloud PC scenario (am I wrong with this assumption?). So, I don't recommend renaming the computer name property of Cloud PCs for whatever reason. I have tested renaming the computer name of the Cloud PC, and it worked fine. I could still log in to Cloud PC. The name change got reflected in the management tools such as Intune and Azure AD. You have options to Export Windows 365 Cloud PC Names. I don't see any supported method to remotely change (mainly for the enterprise version of Cloud PC) the computer name of the Cloud PC from MEM Intune. The Cloud PC remote actions on the MEM admin center portal are different from remote actions for other devices. Thanks for the comments/confirmation from MS!
