Updates fix in-place upgrade to Windows 10 version 1607 problem

Applies to: Windows 10, version 1607, all editionsSystem Center Configuration Manager (current branch - version 1606)Microsoft System Center Configuration Manager (LTSB - version 1606)


When you run an in-place upgrade for Windows 10 version 1607 on a system that's running Microsoft System Center Configuration Manager, the upgrade hangs. This problem occurs while the Upgrade Operating System task is running.


  • No errors are logged in the Configuration Manager or the Windows Setup log files.
  • The SMSTS.log and Setupact.log files stop logging entries.
  • An indicator that a computer is encountering this problem is that Windows Setup hangs during driver inventory. This issue is identified by the following signature in in the setupact.log file under C:\$WINDOWS.~BT\Sources\Panther:

    date time CONX Windows::Compat::Appraiser::WicaDeviceInventory::GetInventory (324): Starting Device Inventory.

    date time CONX Windows::Compat::Appraiser::DriverInventory::GetInventory (204): Starting Driver Inventory.


To fix this issue, install the following update:

4013420 Compatibility update for upgrading to Windows 10 version 1607 and Windows Server 2016: March 14, 2017

Package installation of compatibility updates differs from installation of other Windows updates. To install the compatibility update, follow these steps:

  1. Download the hotfix from the Microsoft Update Catalog website to a new folder on your Windows desktop.
  2. After you download the .cab file, extract its contents to a new folder.
  3. Determine the source directory of your Windows 10 version 1607 installation files. You can find this in the properties of your Upgrade Operating System Package.
  4. After you determine the source directory, copy the contents of the extracted .cab files into the Source folder of the Windows 10 version 1607 installation files. Click Yes to overwrite any existing files.
  5. Update the Distribution Points for the Upgrade Operating System Package.
  6. Retry the deployments and see whether the issue is corrected.