Обновление windows ошибка 4005

In this guide, we are going to discuss how to fix error 0x4005(16389) when upgrading Windows. Several users have reportedly experienced this error code while performing an in-place upgrade to Windows 11/10. The error code says “Unable to make changes to your software” message followed by a long error message when triggered.

This error occurs on SCCM or System Center Configuration Manager while performing an in-place upgrade. SCCM provides great operating system deployment and remote control features that help you perform an in-place upgrade. Or, you can also use it to deploy new operating systems on different devices at a time.

Now, 0x4005(16389) error on SCCM can occur when there are several incompatible applications with Windows 11/10. Although, there can be multiple other reasons that might trigger this upgrade error. In case you are facing the same error code when upgrading Windows, this article will help you out. Here, we bring you various working solutions that will help you fix this error. These fixes reportedly enabled many affected users to fix this error and might just work for you as well. So, let us check out these fixes now.

What causes the 0x4005(16389) error when upgrading Windows?

This error code might be triggered due to various reasons. For every individual, the cause may vary. Here are some common scenarios that result in error code 0x4005(16389) when upgrading Windows:

• This error might be a result of insufficient disk space that is required for upgrading devices. So, if you don’t have enough disk space to perform an in-place upgrade, you should free up the required disk space and then attempt the upgrade again.
• Another reason for this error might be using a different Windows edition to upgrade than the one you are currently using. If the scenario applies to you, choose the same Windows edition to upgrade as your current one.
• If you are using a third-party antivirus, it can prevent the successful completion of the upgrade. So, consider disabling your antivirus to fix the issue.
• In case you are trying to set a local computer description during the task sequence and the command fails, you might receive this error code.

Depending on your scenario, you can try to fix the error by using the suitable fix from the below-listed ones.

Here are the main solutions to try to fix error code 0x4005(16389) when upgrading Windows:

1. Check Disk Space.
2. Disable Third-Party Antivirus.
3. Use Same Windows Edition.
4. Uninstall Program as 32-bit Process on 64-Bit Computers.
5. Change Local Computer Description Command.

1] Check Disk Space

This error may occur in case there is not sufficient disk space on your system that is required for upgrading Windows. It is pretty common that insufficient disk space causes failures and errors when updating or upgrading your Windows PC. So, make sure you have enough space to avoid this error. If the scenario applies to you, you can try freeing up some disk space.

You can free up disk space using the Storage Sense feature or Disk Cleanup utility on Windows 11/10. Apart from that, there are many more ways to clean up disk space. You can also use third-party software like Comet (Managed Disk Cleanup) or Cleanmgr+ to remove junk files and free up some disk space. Additionally, you can also try some free duplicate file finder and remover software that will help you get rid of duplicates and clean up some disk space.

If you have enough disk space and you are still getting this error, try the next potential fix to resolve this error.

Tip: See this post to upgrade devices with less free disk space to Windows.

2] Disable Third-Party Antivirus

If you are using a third-party antivirus software on your PC, consider disabling it before attempting to upgrade your PC. Antivirus software are known to prevent particular actions because of false positive. In case it has suspected certain actions related to the upgrading process as a threat, you might receive this error code. Hence, try disabling your antivirus program and then attempt to initiate the in-place upgrade process. Check if it fixes up the error 0x4005(16389) when upgrading Windows or not.

See: Fix Windows Upgrade Error Code 0xe06d7363

3] Use Same Windows Edition

This error can be a result of using a distinct Windows Edition than the one installed on your system. Some affected users have reportedly fixed this error by selecting the same Windows media. So, make sure you have used the same Windows media as the one you have installed on your system. For example, ensure that you use Windows Enterprise media while upgrading if you are currently on Windows Enterprise edition. See if this was the issue that you needed to take care of.

In case this scenario doesn’t apply to you, move ahead with the next fix on this list.

See: How to use Windows Upgrade Task Sequence to install Multiple Languages.

4] Uninstall Program as 32-bit Process on 64-Bit Computers

This fix is particularly applicable for .NET Deployment only. In case you are facing the error while deploying a .NET framework across the computers, there are chances that the error code is triggered due to programs are running a 32-bit process on your 64-bit architecture computer. If this scenario applies, what you can do is use a particular checkbox inside the installer properties to uninstall the program as 32-bit process on 64-Bit clients. Here are the steps you need to follow to enable this checkbox:

1. Firstly, you need to open the .NET installer or deployment properties that you are currently deploying.
2. Now, inside the Properties box, navigate to the Program tab.
3. Next, turn on the Run installation and uninstall program as 32-bit process on 64-bit clients checkbox.
4. Finally, press the Apply > OK button to save changes, and there try deploying the .NET framework and see if the error is fixed.

If this scenario does not apply to you, try some other fix from this guide.

Read: Fix 0x800707E7 – 0x3000D, The installation failed in the FIRST_BOOT phase error

5] Change Local Computer Description Command

In case you are using a command or script for setting up the local computer description during the upgrade task sequence and the command fails or stops, you are likely to receive this error code. If this scenario suits you, you can try changing the command you used to set the local computer description. You can use a NET CONFIG command for doing this. Simply try adding Run Command-Line to the task sequence and then enter the following command:

cmd /c net config Server /SRVCOMMENT:"%OSDComputerDescription%

This command will set the computer description defined in the OSDComputerDescription variable. You can change the variable name that you want to use.

If none of the mentioned solutions work for you, you can try performing an in-place upgrade using Configuration Manager.

See: Your files, apps, and settings can’t be kept – Windows In-place Upgrade error

How do I perform an in-place upgrade?

To perform an in-place upgrade, you need to download the Windows 10 Installation Media from the Microsoft website. After that, run the executable file ad then select the Upgrade PC Now option to initiate the in-place upgrade process. You then need to follow the on-screen installation guide to complete the process. You can check out the detailed procedure to perform an in-place upgrade.

Hope this guide helps you fix the 0x4005(16389) error when upgrading Windows.

Here are some more posts that might help you:

• Windows places ‘Upgrade block in place’. Are you affected?
• Fix Windows Upgrade Install error 0x80070002 – 0x3000D
• List of Windows Upgrade error codes and solutions.

In this guide, we are going to discuss how to fix error 0x4005(16389) when upgrading Windows. Several users have reportedly experienced this error code while performing an in-place upgrade to Windows 11/10. The error code says “Unable to make changes to your software” message followed by a long error message when triggered.

This error occurs on SCCM or System Center Configuration Manager while performing an in-place upgrade. SCCM provides great operating system deployment and remote control features that help you perform an in-place upgrade. Or, you can also use it to deploy new operating systems on different devices at a time.

Now, 0x4005(16389) error on SCCM can occur when there are several incompatible applications with Windows 11/10. Although, there can be multiple other reasons that might trigger this upgrade error. In case you are facing the same error code when upgrading Windows, this article will help you out. Here, we bring you various working solutions that will help you fix this error. These fixes reportedly enabled many affected users to fix this error and might just work for you as well. So, let us check out these fixes now.

What causes the 0x4005(16389) error when upgrading Windows?

This error code might be triggered due to various reasons. For every individual, the cause may vary. Here are some common scenarios that result in error code 0x4005(16389) when upgrading Windows:

• This error might be a result of insufficient disk space that is required for upgrading devices. So, if you don’t have enough disk space to perform an in-place upgrade, you should free up the required disk space and then attempt the upgrade again.
• Another reason for this error might be using a different Windows edition to upgrade than the one you are currently using. If the scenario applies to you, choose the same Windows edition to upgrade as your current one.
• If you are using a third-party antivirus, it can prevent the successful completion of the upgrade. So, consider disabling your antivirus to fix the issue.
• In case you are trying to set a local computer description during the task sequence and the command fails, you might receive this error code.

Depending on your scenario, you can try to fix the error by using the suitable fix from the below-listed ones.

Here are the main solutions to try to fix error code 0x4005(16389) when upgrading Windows:

1. Check Disk Space.
2. Disable Third-Party Antivirus.
3. Use Same Windows Edition.
4. Uninstall Program as 32-bit Process on 64-Bit Computers.
5. Change Local Computer Description Command.

1] Check Disk Space

This error may occur in case there is not sufficient disk space on your system that is required for upgrading Windows. It is pretty common that insufficient disk space causes failures and errors when updating or upgrading your Windows PC. So, make sure you have enough space to avoid this error. If the scenario applies to you, you can try freeing up some disk space.

You can free up disk space using the Storage Sense feature or Disk Cleanup utility on Windows 11/10. Apart from that, there are many more ways to clean up disk space. You can also use third-party software like Comet (Managed Disk Cleanup) or Cleanmgr+ to remove junk files and free up some disk space. Additionally, you can also try some free duplicate file finder and remover software that will help you get rid of duplicates and clean up some disk space.

If you have enough disk space and you are still getting this error, try the next potential fix to resolve this error.

Tip: See this post to upgrade devices with less free disk space to Windows.

2] Disable Third-Party Antivirus

If you are using a third-party antivirus software on your PC, consider disabling it before attempting to upgrade your PC. Antivirus software are known to prevent particular actions because of false positive. In case it has suspected certain actions related to the upgrading process as a threat, you might receive this error code. Hence, try disabling your antivirus program and then attempt to initiate the in-place upgrade process. Check if it fixes up the error 0x4005(16389) when upgrading Windows or not.

See: Fix Windows Upgrade Error Code 0xe06d7363

3] Use Same Windows Edition

This error can be a result of using a distinct Windows Edition than the one installed on your system. Some affected users have reportedly fixed this error by selecting the same Windows media. So, make sure you have used the same Windows media as the one you have installed on your system. For example, ensure that you use Windows Enterprise media while upgrading if you are currently on Windows Enterprise edition. See if this was the issue that you needed to take care of.

In case this scenario doesn’t apply to you, move ahead with the next fix on this list.

See: How to use Windows Upgrade Task Sequence to install Multiple Languages.

4] Uninstall Program as 32-bit Process on 64-Bit Computers

This fix is particularly applicable for .NET Deployment only. In case you are facing the error while deploying a .NET framework across the computers, there are chances that the error code is triggered due to programs are running a 32-bit process on your 64-bit architecture computer. If this scenario applies, what you can do is use a particular checkbox inside the installer properties to uninstall the program as 32-bit process on 64-Bit clients. Here are the steps you need to follow to enable this checkbox:

1. Firstly, you need to open the .NET installer or deployment properties that you are currently deploying.
2. Now, inside the Properties box, navigate to the Program tab.
3. Next, turn on the Run installation and uninstall program as 32-bit process on 64-bit clients checkbox.
4. Finally, press the Apply > OK button to save changes, and there try deploying the .NET framework and see if the error is fixed.

If this scenario does not apply to you, try some other fix from this guide.

Read: Fix 0x800707E7 – 0x3000D, The installation failed in the FIRST_BOOT phase error

5] Change Local Computer Description Command

In case you are using a command or script for setting up the local computer description during the upgrade task sequence and the command fails or stops, you are likely to receive this error code. If this scenario suits you, you can try changing the command you used to set the local computer description. You can use a NET CONFIG command for doing this. Simply try adding Run Command-Line to the task sequence and then enter the following command:

cmd /c net config Server /SRVCOMMENT:"%OSDComputerDescription%

This command will set the computer description defined in the OSDComputerDescription variable. You can change the variable name that you want to use.

If none of the mentioned solutions work for you, you can try performing an in-place upgrade using Configuration Manager.

See: Your files, apps, and settings can’t be kept – Windows In-place Upgrade error

How do I perform an in-place upgrade?

To perform an in-place upgrade, you need to download the Windows 10 Installation Media from the Microsoft website. After that, run the executable file ad then select the Upgrade PC Now option to initiate the in-place upgrade process. You then need to follow the on-screen installation guide to complete the process. You can check out the detailed procedure to perform an in-place upgrade.

Hope this guide helps you fix the 0x4005(16389) error when upgrading Windows.

Here are some more posts that might help you:

• Windows places ‘Upgrade block in place’. Are you affected?
• Fix Windows Upgrade Install error 0x80070002 – 0x3000D
• List of Windows Upgrade error codes and solutions.

Scenario

You are deploying Windows 10 x64 1607 update. After you click on the update in software center, it looks like everything is working. Files are getting downloaded and whatnot, but you eventually get the error above — Task Sequence: Upgrade to Windows 10 Enterprise x64 1607 has failed with the error code (0x80004005).

After you click «Close» on that, you look back in the software center and it eventually fails with an error code of 0x4005(16389).  It looks something like this:

Troubleshooting

The logs I first looked to were the following client logs:

1. execmgr.log
2. smsts.log
3. dism.log

The execmgr.log showed me that the right task sequence started and that it was running under the NT AUTHORITYSYSTEM user context.

Execution Request for advert  package XXX000EF program * state change from Ready to NotifyExecution execmgr 5/15/2017 8:35:37 AM 8976 (0x2310)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»XXX000EF»,ProgramID=»*», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 5/15/2017 8:35:37 AM 8976 (0x2310)
Executing program as a task sequence. execmgr 5/15/2017 8:35:37 AM 8976 (0x2310)
Executing TS Program execmgr 5/15/2017 8:35:37 AM 8976 (0x2310)
Task Sequence started execmgr 5/15/2017 8:35:37 AM 8976 (0x2310)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = «XXX20058»;
ClientID = «GUID:9E193632-6CBB-4797-AEAA-466E333B6189»;
CommandLine = «»;
DateTime = «20170515143537.173000+000»;
MachineName = «XXXXXX»;
PackageName = «XXX000EF»;
ProcessID = 3484;
ProgramName = «*»;
SiteCode = «XXX»;
ThreadID = 8976;
UserContext = «NT AUTHORITYSYSTEM»;
WorkingDirectory = «C:windowssystem32»;
};

This was helpful because in order for the task sequence to run it has to meet the following conditions:

So it at least told me that #1 was good.  But it didn’t give me much insight as to why the task sequence was failing.  I checked the task sequence itself to see if any reboot switches for any installs were in place — there weren’t any.

I then looked at the SMSTS.LOG and it told me why the task sequence was not finishing.  The files were successfully downloaded, but when SCCM attempted to use DISM to check the WIM Info, it was not able to.

I downloaded the WIM file that was being used and manually ran the DISM /Get-WimInfo against it and received the same error.  So in this case, I needed to either dig further into what was wrong with the WIM file or just create a new Operating System Upgrade Package and add that to the existing task sequence.

For kicks, I took a look at the DISM.LOG to see if I could discern what was wrong. In this case, DISM was unable to read the WIM header.

In the end, I just created a new task sequence using a vanilla copy of the 1607 files (WIM) and then had the task sequence do updates after deploying 1607.  I suspect that something went wrong during the offline servicing of the previous WIM file.

This post helps you to fix Windows Upgrade Failed Error Code 0x4005(16389). You will encounter an issue where a Configuration Manager Windows 10 or Windows 11 in-place upgrade task sequence fails to install in the client computer, SCCM Software Center shows Unable to make changes to software Error Code 0x4005(16389).

The Error Code 0x4005(16389) refereed either it’s insufficient disk space, third party antivirus, required supported windows edition to perform upgrade or hardware, applications are not compatible.

The Software Center error code 0x4005 is generic, and the solution could be different based on the details you get into logs.

If you are performing an upgrade to Windows 11, You can check for compatibility using the PC Health Check app to see if your current PC meets the minimum system requirements to run Windows 11, the recommendation for installing Windows 11 minimum system requirements. 

Your first step is to locate the log file to find details, and Here you will get more details of log files for Windows 10 or Windows 11 Upgrade Process.

• FIX Windows 11 Upgrade Error Code 0xC190010E
• Fix Windows 11 Upgrade Error 0xc11900130
• Windows 11 Migration Guide PowerPoint Word Email Templates for Free Download

The installation failed Error code 0x4005(16389) was received while installing Inplace upgrade from Software Center.

It indicates Unable to make changes to your software, there was a problem applying changes to the software. You can try again, or if the problem continues, the information that is shown in the following section can assist your help desk in troubleshooting.

The software change returned error code 0x4005(16389) with Status Failed.

Several log files are created during each phase of the upgrade process. These log files for Windows 10 or Windows 11 Upgrade Process are essential for troubleshooting upgrade problems before proceeding to the next step,

Note – By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items. 

The most useful log is setupact.log contains information about setup actions. Here you will get inside Down-Level $Windows.~BTSourcesPanther. The log files are located in a different folder depending on the Windows Setup phase. Here you will get more details of log files for Windows 10 or Windows 11 Upgrade Process.

In this scenario, you notice the following highlighted part when you examine Smsts.log files on an affected device –

Running module version 5.0.9058.1000 from location 'C:WINDOWSCCMOSDPrestartCheck.exe'	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Command line: '"OSDPrestartCheck.exe"'	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Checking if at least 4096 MB of computer memory is available	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Memory requirement validation successful (User Required: 4096 MB, Found: 16192 MB)	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
_TS_CRMEMORY=1	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Checking if computer processor speed is at least 1024 MHz	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Processor speed requirement validation successful. (User Required: 1024 MHz, Found: 2808 MHz)	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
_TS_CRSPEED=1	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
Checking if at least 65536 MB free disk space is available	CheckReadiness	1/5/2022 3:47:49 PM	9236 (0x2414)
No drive with the required disk space available. Validation failed

Failed to run the action: Fail TS with OS Upgrade return code. Error -1047526912	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Not in SSL.	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Set a global environment variable _SMSTSLastActionRetCode=-1047526912	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Set a global environment variable _SMSTSLastActionName=Fail TS with OS Upgrade return code	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Clear local default environment	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Let the parent group (Compat Scan Failure) decides whether to continue execution	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Let the parent group (Prepare for Upgrade) decide whether to continue execution	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
The execution of the group (Prepare for Upgrade) has failed and the execution has been aborted. An action failed. Error 0x80004004	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Failed to run the last action: Fail TS with OS Upgrade return code. Result -1047526912. Execution of task sequence failed.	TSManager	1/5/2022 3:48:49 PM	11556 (0x2D24)
Not in SSL.	TSManager	1/5/2022 3:48:50 PM	11556 (0x2D24)
Not displaying the progress UI.	TSManager	1/5/2022 3:48:50 PM	11556 (0x2D24)
Task Sequence Engine failed! Code: enExecutionFail	TSManager	1/5/2022 3:48:50 PM	11556 (0x2D24)
****************************************************************************	TSManager	1/5/2022 3:48:50 PM	11556 (0x2D24)
Task sequence execution failed with error code 80004005	TSManager	1/5/2022 3:48:50 PM	11556 (0x2D24)

FIX Windows Upgrade Failed Error Code 0x4005(16389)

Let’s check the possible solutions to FIX Windows Upgrade Failed Error Code 0x4005(16389). It could be different based on the details you get into logs –

In the above details, you can see it was indicated for the first instance that your PC doesn’t have enough space available to install the upgrade. You need to ensure the device has the required space for a smooth upgrade process. Free some space on the drive and try again Get Tips for Free up drive space in Windows in 5 minutes

There are many ways to free up some disk space to clean unnecessary files. You can also free up disk space Issues automatically with storage sense.

Here you can look at smsts.log once cleanup, Volume C: has the needed disk space. Free disk space user requirement validation successful.

Validate your hardware and software, since the issue has been observed in Windows 11. It would be best to make sure the machine meets the minimum requirements to install Windows 11. If your PC doesn’t meet Windows 11 system requirements, you might encounter an error.

Application compatibility – Applications that work on Windows 10 work on Windows 11. However, it is still a good idea to validate the applications in your environment, particularly any non-Microsoft security or endpoint management solutions, to ensure that they function as expected on Windows 11.

Temporary Disable Installed Third-Party Antivirus – Installed antivirus software may be interfering with Windows Update and causing Windows Update errors. To ensure that the installed third-party antivirus software is not the source of the problem, you can try to temporarily disable this software, and let’s check to trigger the upgrade process.

Suppose you use a command or script inside your upgrade task sequence to set up the local computer description. You also might receive the error in Software Center. I saw this issue reported by a user in TechNet Forum, and resolution is taken from here; you can how to check Set Local Computer Description During Configuration Manager Task Sequence.

You can also share your experience with the different errors and steps taken to resolve them in Comment Section or HTMDForum, which will be helpful for the community members.

Author

About Author – Jitesh, Microsoft MVP, has over five years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.