### Install KMS Client Setup Key for Windows Server 2016 Datacenter Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004f074.md This is an example of the first command in the activation sequence, specifically for Windows Server 2016 Datacenter, showing how to install the KMS client setup key. ```cmd cscript c:\windows\system32\slmgr.vbs /ipk CB7KF-BWN84-R7R2Y-793K2-8XDDG ``` -------------------------------- ### Example of Installing a Service Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/setup-upgrade-and-drivers/create-user-defined-service.md An example command demonstrating the installation of a service named 'Notepad' using Instrsrv.exe and Srvany.exe. ```console C:\\Program Files\\Resource Kit\\Instsrv.exe Notepad C:\\Program Files\\Resource Kit\\Srvany.exe ``` -------------------------------- ### SQL Server Setup Support Files Error Log Example Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/sql/database-engine/install/windows/restore-missing-windows-installer-cache-files.md This log excerpt from _Detail.txt_ shows typical messages related to SQL Server setup, including errors indicating missing installer files and the specific MSI error code 1714. ```output Date/Time Slp: Sco: FileFilePath does not exist Date/Time Slp: Sco: FileFilePathdoes not exist Date/Time Slp: Checkpoint: PREINSTALL_SQLSUPPORT_CPU64_ACTION Date/Time Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machineServer Name Date/Time Slp: Sco: Attempting to open registry subkey Software\Microsoft\Windows\CurrentVersion\Installer Date/Time Slp: Sco: Attempting to get registry value InstallerLocation Date/Time Slp: Windows installer version : 5.0.7601.17514 Date/Time Slp: Sco: Waiting for service 'msiserver' to accept the stop request. Date/Time Slp: Sco: Attempting to open SC Manager Date/Time Slp: Sco: Attempting to open service handle for service msiserver Date/Time Slp: Invoking QueryServiceStatus Win32 API Date/Time Slp: Sco: Attempting to close service handle for service msiserver Date/Time Slp: Sco: Attempting to close SC Manager Date/TimeSlp: Target package: "FilePath" Date/TimeSlp: MSI Error: 1714 The older version of Microsoft SQL Server 2012 Setup (English) cannot be removed. Contact your technical support group. Date/TimeSlp: InstallPackage: MsiInstallProduct returned the result code 1603. Date/TimeSlp: Using MSI error code to detect the retry option: 1714 Date/TimeSlp: No retry-able MSI return code detected. ``` -------------------------------- ### Install KMS Client Setup Key Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/windows/windows-vm-activation-error-0xc004c003.md Use this command to set the appropriate KMS client setup key for your Windows version. Replace the example key with the one relevant to your Windows edition. ```cmd cscript c:\windows\system32\slmgr.vbs /ipk WX4NM-KYWYW-QJJR4-XV3QB-6VM33 ``` -------------------------------- ### Example: Install DHCP Server Core using Ocsetup.exe Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/setup-upgrade-and-drivers/use-ocsetup-to-install-remove-components.md This is an example of how to install the DHCP Server role using Ocsetup.exe. The component name 'DHCPServerCore' is case-sensitive. ```batch start /w ocsetup DHCPServerCore ``` -------------------------------- ### MSI Logging: Verbose Logging Start Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/troubleshoot-install-application-step.md Example log entry from MSI Logging.log indicating the start of verbose logging for an MSI installation. ```log === Verbose logging started: 1/13/2016 17:56:45 Build type: SHIP UNICODE 5.00.9600.00 Calling process: C:\WINDOWS\system32\msiexec.exe === ``` -------------------------------- ### Start Office Installation Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/how-to-download-office-install-not-in-vlsc.md Use this command to begin the Office LTSC installation process after preparing the configuration file. Ensure you are in the correct directory. ```cmd Setup /configure configuration.xml ``` -------------------------------- ### Example MSI Log Entry with Transform Errors Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md This log entry illustrates a common issue where Setup cannot apply a transform file due to incorrect paths. It shows the installer searching both a local path and a network share before failing. ```text MSI (c) (A5:65): Looking for file transform: c:\test.mst MSI (c) (A5:65): Note: 1: 2203 2: c:\test.mst 3: -2147287038 MSI (c) (A5:65): Couldn't find cached transform c:\test.mst. Looking for it at the source. MSI (c) (A5:65): Looking for file transform: \\server\share\2003_ADMIN\test.mst MSI (c) (A5:65): Note: 1: 2203 2: \\server\share\2003_ADMIN\test.mst 3: -2147287038 MSI (c) (A5:65): Note: 1: 2729 1: 2203 2: \\server\share\2003_ADMIN\test.mst 3: -2147287038 Error applying transforms. Verify that the specified transform paths are valid. \\server\share\2003_ADMIN\test.mst MSI (c) (A5:65): MainEngineThread is returning 1624 ``` -------------------------------- ### IIS 7.x Setup Log Entry Example Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/developer/webapps/iis/www-administration-management/troubleshooting-iis-7x-installation-issues.md This log entry shows a typical failure during IIS 7.0 Component Based Setup, indicating a problem with installing the FTPServer component due to a specific error code (0x800708c5). ```output [11/12/2010 19:48:13] [ ***** IIS 7.0 Component Based Setup ***** ] [11/12/2010 19:48:13] "C:\Windows\System32\inetsrv\iissetup.exe" /install FTPServer [11/12/2010 19:48:13] < !!FAIL!! > METABASE_UTIL::InstallFtpMetabaseEntries result=0x800708c5 [11/12/2010 19:48:13] < !!FAIL!! > Install of component FTPServer result=0x800708c5 [11/12/2010 19:48:13] < !!FAIL!! > COMPONENT::ExecuteCommand result=0x800708c5 [11/12/2010 19:48:13] [ End of IIS 7.0 Component Based Setup ] ``` -------------------------------- ### Example Boot.ini File Content Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-server/performance/troubleshoot-ntldr-is-missing-error.md This is an example of the Boot.ini file content before modification, showing the temporary Windows installation path. ```ini [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN [operating systems] multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows 2000 Professional" /fastdetect ``` -------------------------------- ### SQL Server Setup Log - Package Not Installed Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/sql/database-engine/install/windows/restore-missing-windows-installer-cache-files.md Entries in the Slp.exe setup log indicating that a package is not installed and that the expected MSI file does not exist at the specified location. ```output Slp: Package ID sql_xxx_xxx_xxx: NotInstalled Slp: Sco: File 'X:\x64\setup\x64\xxx_xxx_xxx.msi' does not exist Slp: Sco: File 'X:\x64\setup\x64\xxx_xxx_xxx.msi' does not exist ``` -------------------------------- ### Office MSI Installation Command Line Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md Example command line for installing Office using MSI, specifying installation source, logging, and company name. ```Command Line /I \\server\share\2003_Admin\PRO11.MSI METRICSSOURCE="\\server\share\2003_Admin companyname=\"contoso\" /qb" companyname="contoso" LAUNCHEDFROMSETUP=1 SETUPEXEPATH=\\server\share\2003_Admin\ /qb ``` -------------------------------- ### Running Setup with Adminfile Option Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/mdt/troubleshooting-reference.md This command demonstrates how to run setup.exe with a specified adminfile (MSP) for patching. Ensure the paths to setup.exe and the MSP file are correct. ```cmd cmd: \\Server\Deployment$\Tools\X86\bddrun.exe \\Server\Share\Microsoft\Office\2007\Professional\setup.exe /adminfile \\Server\Share\Microsoft\Office\2007\Professional\file.msp ``` -------------------------------- ### AppDiscovery Log Entry for Application Install Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/troubleshoot-install-application-step.md Example log entry from AppDiscovery.log showing the start of an application install enforcement for a specific deployment type. ```log ActionType - Install,Max execute time = 120 minutes for AppDT "ConfigMgr 2012 Toolkit R2 - Windows Installer (*.msi file)" [ScopeId_GUID/DeploymentType_GUID], Revision - 6 ``` -------------------------------- ### Windows Installer Log Entry for Error 1603 Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md Example log output indicating a Windows Installer error (return code 1603) during a chained setup process. This signifies a problem with the Windows Installer component. ```AsciiDoc 9/22/03 3:34:27 PM Chained install return code: 1603 Shutting down chained setup processing. Set Verbose logging for subsequent setup. ***** Setup exits 9/22/03 3:34:27 PM (return = 1603) ``` -------------------------------- ### Office Setup Log: Command Line Parameters Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md This snippet shows how command-line properties and switches, such as 'companyname' and '/qb', are logged during Office setup. It's crucial for verifying that the correct parameters were passed and recognized. ```output Launch Setup 9/22/03 1:49:46 PM companyname="contoso" /qb Detected Windows Info: PlatformId = 2 MajorVersion = 4 MinorVersion = 0 Setup path: \\server\share\2003_Admin\SETUP.EXE Adding property...companyname="contoso" Recognized command line switch: /qb -and-Office-specific properties added: companyname="contoso" General properties added: LAUNCHEDFROMSETUP=1 SETUPEXEPATH=\\server\share\2003_Admin\ Writing Task: D:\WINNT\System32\msiexec.exe ``` -------------------------------- ### Setupact.log Entries for OEM License Detection (In-Place Upgrade) Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/os-deployment-task-sequence-not-continue.md These log entries show that both client OS and OEM licensing are detected, and since it's not an enterprise edition, 'SetupComplete.cmd' is explicitly not run during the 'Upgrade Operating System' step. ```text [windeploy.exe] Client OS detected: 1 [windeploy.exe] OEM Licensing detected: 1 [windeploy.exe] EnterpriseS or Enterprise or EnterpriseSN or EnterpriseN edition detected: 0 [windeploy.exe] Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd [windeploy.exe] Not allowed to run the Setupcomplete.cmd, will not run SetupComplete.cmd ``` -------------------------------- ### Example DPM TriggerJob Command Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/system-center/dpm/troubleshoot-scheduled-backup-job-failures.md An example of a typical command executed by SQL Server Agent to start a backup job. The path to TriggerJob.exe may vary based on DPM version and installation type. ```console C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\TriggerJob.exe 1bd305ae-f158-4948-93f8-e935103b168f 1e53fd39-0339-4d41-96ec-89fdf587f1e5 ``` -------------------------------- ### Example smsts.log Entries for Error 80070005 Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/osd-task-sequence-fails-error-80070005.md These log entries from smsts.log indicate the 'Setup Windows and ConfigMgr' step failing due to an access denied error (80070005) when trying to install the OSD setup hook. ```log OSDSetupWindows Installing hook to 'C:\\WINDOWS' OSDSetupWindows Command line for extension .EXE is "%1" %* OSDSetupWindows Set command line: "X:\\sms\\bin\\x64\\OSDSETUPHOOK.EXE" "/install:C:\\WINDOWS" /version:10.0 OSDSetupWindows Executing command line: "X:\\sms\\bin\\x64\\OSDSETUPHOOK.EXE" "/install:C:\\WINDOWS" /version:10.0 OSDSetupHook Installing OSD setup hook OSDSetupHook !shCmdFile.null(), HRESULT=80070005 (..\\vistasetuphook.cpp,96) OSDSetupHook Failed to install the setup hook. Permissions on the requested may be configured incorrectly. Access is denied. (Error: 80070005; Source: Windows) OSDSetupHook pHook->install(sWindowsDir), HRESULT=80070005 (..\\osdsetuphook.cpp,385) OSDSetupHook Failed to install OSD setup hook (0x80070005) OSDSetupWindows Process completed with exit code 2147942405 OSDSetupWindows exitCode, HRESULT=80070005 (setupwindows.cpp,785) OSDSetupWindows Install setup hook failed with error code (80070005). OSDSetupWindows this->installSetupHook(), HRESULT=80070005 (setupwindows.cpp,452) OSDSetupWindows Failed to install setup hook (80070005) OSDSetupWindows setup.run(), HRESULT=80070005 (setupwindows.cpp,1650) OSDSetupWindows Exiting with code 0x80070005 TSManager Process completed with exit code 2147942405 TSManager !-----------------------------------------------------------------------! TSManager Failed to run the action: Setup Windows and ConfigMgr. Permissions on the requested may be configured incorrectly. Access is denied. (Error: 80070005; Source: Windows) ``` -------------------------------- ### Setupact.log Entry for OEM License Detection (Refresh/New Computer) Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/os-deployment-task-sequence-not-continue.md This log entry indicates that the 'SetupComplete.cmd' script is being skipped because an OEM license was detected during the 'Setup Windows and ConfigMgr' step of a task sequence. ```text [windeploy.exe] OEM license detected, will not run SetupComplete.cmd ``` -------------------------------- ### Sample Setup Log Analysis Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/sql/database-engine/install/windows/restore-missing-windows-installer-cache-files.md Examine setup log files to identify the original MSP file used by a patch and potential installation errors. ```output MSI (s) (FC:F8) [13:48:58:649]: Opening existing patch 'C:\WINDOWS\Installer\145258.msp'. MSI (s) (FC:F8) [13:48:58:649]: Couldn't find local patch 'C:\WINDOWS\Installer\145258.msp'. Looking for it at its source. MSI (s) (FC:F8) [13:48:58:649]: Resolving Patch source. MSI (s) (FC:F8) [13:48:58:649]: Note: 1: 2203 2: D:\cda162709d239766830bae5ce12b\HotFixSQL\Files\sqlrun_sql.msp 3: -2147287037 MSI (s) (FC:F8) [13:48:58:649]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (s) (FC:F8) [13:49:29:961]: Product: Microsoft SQL Server 2005 -- Installation failed. MSI (s) (FC:F8) [13:49:29:992]: MainEngineThread is returning 1635 This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package. D:\SQL2K5\Servers\Setup\SqlRun_SQL.msi ``` -------------------------------- ### Stale Product Code Error During Entra Connect Installation Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/entra/entra-id/user-prov-sync/troubleshoot-aad-connect-fails-to-install-upgraded-version.md This log shows an 'unrecognized error (1608)' when trying to get product information, indicating a stale product code in Windows Installer. This prevents the setup wizard from correctly detecting the installed sync engine. ```output [15:29:06.958] [ 1] [INFO ] Performing direct lookup of upgrade codes for: Azure AD Sync Engine [15:29:06.959] [ 1] [VERB ] Getting list of installed packages by upgrade code [15:29:06.959] [ 1] [INFO ] GetProductInfoProperty({7c4397b7-9008-4c23-8cda-3b3b8faf4312}, VersionString): unrecognized error (1608) [15:29:06.959] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {545334d7-13cd-4bab-8da1-2775fa8cf7c2}: stale product code {7c4397b7-9008-4c23-8cda-3b3b8faf4312}. [15:29:06.959] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {545334d7-13cd-4bab-8da1-2775fa8cf7c2}: no registered products found. [15:29:06.959] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {dc9e604e-37b0-4efc-b429-21721cf49d0d}: no registered products found. [15:29:06.959] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {bef7e7d9-2ac2-44b9-abfc-3335222b92a7}: no registered products found. [15:29:06.963] [ 1] [INFO ] Determining installation action for Azure AD Sync Engine (545334d7-13cd-4bab-8da1-2775fa8cf7c2) [15:29:07.059] [ 1] [INFO ] Product Azure AD Sync Engine is not installed. ``` -------------------------------- ### Office Setup Log: Files to Download Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md This snippet shows a sample of files that Setup.exe logs as being copied to the \MSOCACHE folder during an Office installation. It helps in identifying which installation files are being processed. ```output File: FILES\WINDOWS\INF\AER_1033.ADM (DW20.ADM_1033) File: FILES\PFILES\COMMON\MSSHARED\DW\DW20.EXE (DW20.EXE_0001) File: FILES\PFILES\COMMON\MSSHARED\DW\DWDCW20.DLL (DWDCW20.DLL) File: FILES\PFILES\COMMON\MSSHARED\DW\1033\DWINTL20.DLL (DWINTL20.DLL_0001_1033) File: FILES\PFILES\COMMON\MSSHARED\DW\DWTRIG20.EXE (DWTRIG20.EXE) File: FILES\PFILES\MSOFFICE\OFFICE11\OCLEAN.DLL (OCLEAN.DLL_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCORE.OPC (OCLNCORE.OPC_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCUST.OPC (OCLNCUST.OPC_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\1033\OCLNINTL.OPC (OCLNINTL.OPC_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\OFFCLN.EXE (OFFCLN.EXE_1033) File: FILES\SETUP\OSE.EXE (OSE.EXE) File: PRO11.MSI (PRO11.MSI) File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10O.CHM (PSS10O.CHM_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10R.CHM (PSS10R.CHM_1033) File: FILES\PFILES\MSOFFICE\OFFICE11\1033\SETUP.CHM (SETUP.CHM_1033) File: SKU011.XML (SKU011.XML_0002_1033) File: A2561405.CAB (A2561405.CAB) File: A3561405.CAB (A3561405.CAB) File: A4561405.CAB (A4561405.CAB) File: AV561403.CAB (AV561403.CAB) File: CC561401.CAB (CC561401.CAB) ``` -------------------------------- ### Example: Searching for Error 1327 in Windows Installer Logs Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md When encountering an error message during setup, search the log file for the specific error number. This example shows how to find and interpret logs related to 'Error 1327' and 'Invalid Drive'. ```output MSI (c) (41:90): Note: 1: 1327 2: C:\ Error 1327. Invalid Drive: C:\ MSI (c) (41:90): Product: System Files Update -- Error 1327. Invalid Drive: C:\ Action ended 15:34:26: CostFinalize. Return value 3. ``` -------------------------------- ### Create a Pod with an Nginx Image Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/azure-kubernetes/create-upgrade-delete/pod-stuck-crashloopbackoff-mode.md This example shows the creation of a pod using the `nginx` image, which typically runs successfully and remains in a Running state. ```bash kubectl run nginx --image nginx ``` -------------------------------- ### MSIEXEC.log Error Example Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/windows/windows-azure-guest-agent.md This log snippet shows a common error (1722) encountered during Guest Agent installation, indicating a problem with a program run as part of the setup. ```log Action start 12:11:03: CA2. MSI (s) (7C:A8) [12:27:20:328]: Note: 1: 1722 2: CA2 3: wscript.exe 4: "C:\Program Files\Windows Azure VM Agent v2.7.41491.949\InstallOrUpdateGA.vbs" MSI (s) (7C:A8) [12:27:20:328]: Note: 1: 2205 2: 3: Error MSI (s) (7C:A8) [12:27:20:328]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722 CustomAction CA2 returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (7C:A8) [12:27:22:707]: Note: 1: 2205 2: 3: Error MSI (s) (7C:A8) [12:27:22:707]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (7C:A8) [12:27:22:707]: Product: Windows Azure VM Agent - 2.7.41491.949 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CA2, location: wscript.exe, command: "C:\Program Files\Windows Azure VM Agent v2.7.41491.949\InstallOrUpdateGA.vbs" ``` -------------------------------- ### Recommended SBD configuration parameters Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/linux/troubleshoot-sbd-issues-rhel.md This is an example of the recommended parameters for the `/etc/sysconfig/sbd` configuration file. Ensure these settings and the SBD_DEVICE paths are correct for your environment. ```output SBD_PACEMAKER=yes SBD_STARTMODE=always SBD_DELAY_START=no SBD_WATCHDOG_DEV=/dev/watchdog SBD_WATCHDOG_TIMEOUT=5 SBD_TIMEOUT_ACTION=flush,reboot SBD_MOVE_TO_ROOT_CGROUP=auto SBD_OPTS= SBD_DEVICE="/dev/disk/by-id/scsi-360014056eadbecfeca042d4a66b9d77;/dev/disk/by-id/scsi-36001405cbac988092e448059d25d1a4a;/dev/disk/by-id/scsi-36001405a29a443e4a6e4ceeae822e5eb" ``` -------------------------------- ### Example VM Agent Log Entry for VMAccess Extension Error Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/windows/support-agent-extensions.md This log entry shows an example of an error encountered when the VMAccess extension fails to start within the specified timeout. It indicates a potential issue with the extension's installation or startup process. ```log [00000019] [04/08/2014 23:25:06.83] [INFO] plugin (name: Microsoft.Compute.VMAccessAgent, version: 1.0.3) enabled successfully., Code: 0 [00000028] [04/08/2014 23:25:07.80] [INFO] Successfully installed plugin Microsoft.Compute.BGInfo 1.1. [00000028] [04/08/2014 23:25:07.80] [INFO] plugin (name: Microsoft.Compute.BGInfo, version: 1.1) enabled successfully. Code: 0 [00000003] [04/08/2014 23:27:04.11] [ERROR] Install command of Microsoft.Compute.VMAccessAgent has not exited on time! Killing it... ``` -------------------------------- ### Windows Setup Command Line Log Excerpt Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md This log entry displays the command line used by Windows Setup, including parameters for product, pre-download, package, priority, and dynamic update settings. It also shows paths for language packs and scripts. ```output YYYY-MM-DD HH:MM:SS, Info MOUPG SetupHost::Initialize: CmdLine = [/Product Client /PreDownload /Package /Priority Normal /Quiet /ReportId 96CEE****************3-2D4E1B1306F5.1 /FlightData "RS:24944" "/CancelId" "C-757a2**********************4256ca34" "/PauseId" "P-757a20**********************" "/CorrelationVector" "otIKT***B0mTOyAl.1.1.28.4" "/DownloadSizeInMB" "3046" /InstallLangPacks C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\LP /PostOOBE C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\SetupComplete.cmd /PostRollback C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\ErrorHandler.cmd /DynamicUpdate Disable /Compat IgnoreWarning] ``` -------------------------------- ### Get PolyBase Version (Windows, Service Not Running) Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/sql/releases/components-client-tools-versions.md Use PowerShell to find the file version of the PolyBase executable if the service is not running or cannot be started on Windows. It searches the default SQL Server installation directory. ```powershell cd 'C:\Program Files\Microsoft SQL Server' ls mpdwsvc.exe -r -ea silentlycontinue | % versioninfo | Format-Table -AutoSize ``` -------------------------------- ### Example pkg-ref structure for install-location Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/intune/app-management/macos-lob-apps-not-deployed.md This example shows the expected structure within the extracted pkg-info file, specifically highlighting the 'version' and 'customLocation' attributes. Ensure the 'customLocation' is set to '/Applications' or a subfolder. ```xml ``` -------------------------------- ### NTFRS Logging Level 4 Example (NULL File System GUID) Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-server/networking/ntfrs-error-event-13559-replication-stops.md This example illustrates a scenario where the File System GUID is reported as NULL during NTFRS logging at level 4. This condition, similar to the previous example, points to a GUID mismatch and can lead to event 13559. ```text :S: Oid for replica root is 00000000-0000-0000-0000000000000000 ERROR - Replica root guid mismatch for Replica Set (DOMAIN SYSTEM VOLUME (SYSVOL SHARE)) ERROR - Replica root guid (FS) (00000000-0000-0000-0000000000000000) ERROR - Replica root guid (DB) (17358178-8dd7-47e5-8ec1642bbc6ba318) ERROR - Replica Set (DOMAIN SYSTEM VOLUME (SYSVOL SHARE)) is marked to be deleted ``` -------------------------------- ### AppEnforce Log Entry: Starting Install Enforcement Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/mem/configmgr/os-deployment/troubleshoot-install-application-step.md AppEnforce.log entry indicating the start of install enforcement for an application deployment type and its initial detection status. ```log 01-13-2016 17:56:43.104 AppEnforce 2216 (0x8a8) +++ Starting Install enforcement for App DT "ConfigMgr 2012 Toolkit R2 - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_GUID/DeploymentType_GUID, Revision - 6, ContentPath - C:\WINDOWS\ccmcache\1, Execution Context - Any 01-13-2016 17:56:44.666 AppEnforce 2216 (0x8a8) +++ Application not discovered. [AppDT Id: ScopeId_GUID/DeploymentType_GUID, Revision: 6] ``` -------------------------------- ### Enable Complete Verbose Logging When Setup Hangs Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/Office/Client/installation/office-setup-issues.md Run this command line to enable complete verbose logging when Office Setup stops responding. The `!` option ensures logging information is written line by line, minimizing data loss. Replace `` with the full path of your Office source location. ```command-line \Setup.exe /L*v! C:\Verboselog.txt ``` -------------------------------- ### Install an application using winget Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/shell-experience/troubleshooting-microsoft-store-apps-download-failure.md Use the `winget install` command to install an application found via search. Replace `` with the name of the application you wish to install. ```powershell winget install ``` -------------------------------- ### Example: Unlock Drive F with GUID BEK File Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/windows/unlock-encrypted-disk-offline.md An example of the manage-bde unlock command for drive F using a BEK file with a GUID name. ```console manage-bde -unlock F: -RecoveryKey C:\BEK\EF7B2F5A-50C6-4637-9F13-7F599C12F85C.BEK ``` -------------------------------- ### Manually Launch Setup.exe from USB Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/setup-upgrade-and-drivers/limitations-dollar-sign-winpedriver-dollar-sign.md This command is used to manually launch the Windows Setup executable from the OS installation source files copied to the USB drive. Appropriate switches can be added as needed. ```batch %usbdrv%\\\\Sources\\Setup.exe ``` -------------------------------- ### Display lsblk output example Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/linux/collect-performance-metrics-from-a-linux-system.md Shows an example of the output generated by the 'lsblk' command, illustrating disk and partition configurations. ```output NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 300G 0 disk └─sda1 8:1 0 300G 0 part /mnt sdb 8:16 0 30G 0 disk ├─sdb1 8:17 0 1M 0 part ├─sdb2 8:18 0 200M 0 part /boot/efi ├─sdb3 8:19 0 1G 0 part /boot └─sdb4 8:20 0 28.8G 0 part / zram0 252:0 0 16G 0 disk [SWAP] ``` -------------------------------- ### Start TSS PERF and SETUP Traces Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-client/system-management-components/windows-error-reporting-diagnostics-enablement-guidance.md Use this cmdlet to start performance and setup traces with the TSS tool. Ensure TSS is extracted to C:\tss and run from an elevated PowerShell prompt. ```powershell TSS.ps1 -SDP PERF,SETUP ``` -------------------------------- ### IN Operator for Guid Properties Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/system-center/scom/regular-expression-support.md Use the IN operator to check if a Guid property's value is present in a list of Guids. Example checks if Id is one of the two provided Guids. ```text Id IN ('aaaabbbb-0000-cccc-1111-dddd2222eeee', 'bbbbcccc-1111-dddd-2222-eeee3333ffff') Evaluates to true if the value of the `Id` property is one of the two globally unique identifiers provided. ``` -------------------------------- ### Install KMS Client Product Key Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-server/licensing-and-activation/troubleshoot-adba-clients-not-activate.md Use the `slmgr /ipk` command to install a generic KMS client setup key for a specific Windows Server version. This is often a necessary step before forcing activation. ```batch slmgr /ipk ``` -------------------------------- ### Example fstab entry with UUID and nofail option Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/linux/linux-virtual-machine-cannot-start-fstab-errors.md This example shows how to mount a data disk using its UUID and the 'nofail' option to ensure the VM continues to boot even if the disk has issues. ```bash UUID= /data xfs defaults,nofail 0 0 ``` -------------------------------- ### Successful Agent Installation Log Entry Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/azure-monitor/azure-monitor-agent/windows-agents/resolve-windows-agent-installation-issues.md This is an example of a successful installation log entry from the MMA extension installation log. It indicates the agent was installed successfully and the service is running. ```output 11/22/2019 1:10:05 AM +00:00 Starting installation of agent install package at path *C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.18018.0\MOMAgent.msi with log C:\WindowsAzure\Logs\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\1.0.18018.0\MMAExtensionInstall0-Setup0.log*. 11/22/2019 1:11:42 AM +00:00 Windows installer reported success in installing agent. 11/22/2019 1:11:42 AM +00:00 Verified that service Microsoft Monitoring Agent is installed and in Running state. 11/22/2019 1:11:42 AM +00:00 Completed installing the Microsoft Monitoring Agent VM Extension. ``` -------------------------------- ### View Installed RPM Packages Output Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md Example output listing installed cloud-region related packages. ```output cloud-regionsrv-client-9.1.5-6.43.1.noarch cloud-regionsrv-client-plugin-azure-1.0.1-6.43.1.noarch ``` -------------------------------- ### Example: Load ASP Driver .ini File Source: https://github.com/microsoftdocs/supportarticles-docs/blob/main/support/windows-server/performance/rebuild-performance-counter-library-values.md An example demonstrating how to load the ASP driver's performance counter library using its corresponding .ini file, Axperf.ini. ```console lodctr axperf.ini ```