80244007 ошибка обновления windows server 2012 r2

80244007 windows update 2012r2

Am 29.04.2016 schrieb june8807:

You are sure about the Servername?

Try on one Testclient in a Commandline open with admin rights:

net stop wuauserv
rd /s /q %windir%SoftwareDistribution
del %windir%WindowsUpdate.log
net start wuauserv
wuauclt /detectnow
wuauclt /reportnow
Wait 10 Minutes, now run Windows Update again. If it is not working,
have a look in %windir%WindowsUpdates.log for errormessages.

Check the windows Firewall for outgoing port 8530 and on the WSUS
incoming port 8530.

Hello! Thank you for your answer.

yes, dns name is ok.

unfortunatly, i can not delete WindowsUpdate.log

C:> del %windir%WindowsUpdate.log
C:WindowsWindowsUpdate.log
The process cannot access the file because it is being used by another process.

Of cause, windows update was stoped.

Magic! It works now!

Should I do «rd /s /q %windir%SoftwareDistribution» on every client? Or there ia any other way?

Am 29.04.2016 schrieb june8807:

No, it is not. wsus.domain is not complete.

wsus or wsus.domain.tld
Better Way is http://yourWSUS:8530
If DNS is working, your clients must find WSUS.

C:> del %windir%WindowsUpdate.log
C:WindowsWindowsUpdate.log
The process cannot access the file because it is being used by another process.

Of cause, windows update was stoped.

Not magic. In this cas you can stop BITS too.

Should I do «rd /s /q %windir%SoftwareDistribution» on every client? Or there ia any other way?

If this help for you, yes you have to do this on each client.

Download and install the latest WU-Agent on this Client.
https://support.microsoft.com/en-us/kb/949104

Are all Updatess on your Mainstream-WSUS allready downloaded?

Unfortunatly we have historical singlelabel domain. so, wussrvr.domain is its dns.

Wuaueng.dll on win 2012r2 clients is 7.9.9600.18192

Wuaueng.dll on win 7(x64) is 7.6.7601.19161

Are all Updatess on your Mainstream-WSUS allready downloaded?

We have only one WSUS. That uses TMG proxy for downloading from MS

This is one more question

Updating needing files:4

Downloaded 2591.09 Mb of 11466.11 Mb

This 2.5 Gb was downloaded, and more than sereral hours I have no progress.

8Gb? It is updates, that has not been approved (migration to win10)

Am 30.04.2016 schrieb june8807:

Unfortunatly we have historical singlelabel domain. so, wussrvr.domain is its dns.

Uiuiui, it should running with WSUS-Name only.

Wuaueng.dll on win 2012r2 clients is 7.9.9600.18192

Wuaueng.dll on win 7(x64) is 7.6.7601.19161

You can run a Computerstartupscript an do so:

Am 30.04.2016 schrieb june8807:

Are all Updatess on your Mainstream-WSUS allready downloaded?

We have only one WSUS. That uses TMG proxy for downloading from MS

This is one more question

Updating needing files:4

Downloaded 2591.09 Mb of 11466.11 Mb

This 2.5 Gb was downloaded, and more than sereral hours I have no progress.

8Gb? It is updates, that has not been approved (migration to win10)

Hello! Thank you for your answer/support!

So, my desision was restore from backup (600 gb from tape), and re-do migration from WID to SQLexpress.

Now everything is fine. My mistake was, that I deleted «old» IIS Site (application) and re create new one.

This time I did not delete it. Just swithed to new SQL instance in registry only.

And, migic!, my old WSUS IIS site (application) got stable, no more falting.

Источник

How to Fix Windows Update Error 0x80244007?

Several Windows users have been getting the 0x80244007 error code when trying to install certain updates using the WU (Windows Update) function. In most cases, affected users are seeing the ‘There were some problems installing updates, but we’ll try again later’ error message. As it turns out, this error code is more common on Windows 10, but there are some occurrences of it occurring on Windows 8.1.

Windows Update Error 0x80244007

What’s causing the 0x80244007 error code?

We investigated this particular issue by looking at various user reports and testing out different repair strategies that are commonly recommended by other affected users. As it turns out, several different causes might trigger the 0x80244007 error code. Here’s a list of potential culprits:

Method 1: Running the Windows Update Troubleshooter

Before you try out different repair strategies, let’s see if your operating system is not capable of resolving the issue automatically. If the issue you’re encountering is happening due to an inconsistency that’s already documented by Microsoft, chances are the fix is as simple as running the Windows Update troubleshooter.

The Windows Update Troubleshooter is a utility that contains a selection of repair strategies that can be automatically applied in case a covered scenario is uncovered. Several Windows users that were also encountering the 0x80244007 error code have reported that the issue was resolved after they ran this troubleshooter and restarted their computer.

Here’s a quick guide on running the Windows Update Troubleshooter to fix the 0x80244007 error:

If you’re still encountering the same error code as the update fails, move down to the next method below.

Method 2: Running DISM and SFC Scans

If the first method didn’t work for you, the issue is likely facilitated by some kind of System File corruption. Since WU (Windows Update) works closely with a lot of dependencies, a lot of different files might be triggering this error code.

If this scenario is applicable, the most efficient way of resolving the problem is to run a couple of utilities capable of fixing both logical errors and system file corruption. SFC (System File Checker) and DISM (Deployment Image Servicing and Management) are both capable of doing this.

DISM uses a sub-component of WU to replace corrupted instances with healthy copies, while SFC makes use of a locally stored copy to do the same thing.

Since both utilities go about fixing corrupted instances in different ways, we recommend that you run both to fix the 0x80244007 error. Here’s a quick guide on doing this:

If the same issue 0x80244007 error is still occurring, move down to the next method below.

Method 3: Uninstalling overprotective 3rd party suite

As it turns out, another potential cause that might trigger the 0x80244007 error when you’re trying to install a pending Windows Update is an overprotective AV suite. According to several user reports, several 3rd party security suites have the potential of blocking the connection between the WU component and the external server. Sophos, McAffee, AVAST, Comodo and a few others are commonly reported for the facilitation of the apparition of this issue.

If you’re currently using a security scanner that you think might be responsible for this error code, you should be able to circumvent the problem either by disabling the real-time protection while the update is installed or by uninstalling the AV suite altogether and moving towards the built-in solution (Windows Defender).

First things first, you should start by trying to disable the real-time protection of your AV. This procedure will be different depending on the 3rd party client that you’re using. But, in most cases, you can do this by making use of the taskbar icon. Right-click on it and look for an option that will disable the real-time protection.

Disabling the real-time protection on Avast Antivirus

As soon as the real-time protection is disabled, attempt to install the update again and see if you can install the update without seeing the 0x80244007 error.

If the same issue is still occurring, you should uninstall the AV completely, remove any remnant files and restart your computer to see if the issue has been resolved. If you decide to do this, follow this article (here). Use it as a walk-through through the steps of installing your security program without leaving behind any leftover files that might still trigger the same issue.

If this method is not applicable or you’ve already followed the steps below to no avail, move down to the next method below.

Method 4: Resetting all Windows Update components

If the first 3 methods didn’t provide you with a breakthrough that allowed you to install the Windows Update without issues, likely, you’re dealing with a WU system file inconsistency that’s hindering your machine’s ability to update. If multiple updates are failing with the same error code, it’s even more evidence that this scenario is applicable.

In this case, you should be able to resolve the issue by resetting all Windows components and dependencies that are involved in this process. A few users that were also encountering this problem have confirmed that the steps below have allowed them to resolve the 0x80244007 error.

Here’s a step-by-step guide on resetting all Windows Update components manually via an elevated Command Prompt:

If the same error code is still showing and you’re still unable to complete the installation of the update, move down to the final method below.

Method 5: Perform a repair install

If none of the potential fixes above have worked for you, you’re likely dealing with an underlying system file corruption issue that cannot be resolved with standard recovery procedures. In situations like this one, your best hope of resolving the issue is to reset every Windows component to ensure that your OS is free of corruption.

When it comes to refreshing every OS component, the easiest way is to perform a clean install. But keep in mind that this operation will also delete most of your files including app & game installation, user preferences and any personal media stored on the Windows drive.

If you want the damage-controlled approach, you should go for a repair install (in-place repair) instead. This procedure is a little more tedious, but it will allow you to reset every component of your Windows installation while allowing you to keep all your files (including apps, games, user preferences, personal media, etc.).

Источник

Fix Windows Update error 0x80244007 on Windows 10

Windows Update errors aren’t uncommon. Some are easy to resolve, while others need a lot of time and research towards resolutions. One such tough to fix case is with Windows Update Error 0x80244007. This error simply halts the Windows Update process and restarting the system doesn’t help much.

Windows Update Error 0x80244007

The description of the error is “SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes.” The main cause behind the issue is that Windows is unable to renew the cookies for Windows Update.

If you face this issue, you can try the following suggestions:

1] Run the Windows Update troubleshooter

The Windows Update troubleshooter would review the status of the services which support the process. It would prompt and fix if anything abnormal is detected. The procedure to run the Windows Update troubleshooter is as follows:

Click on Start > Settings > Updates and Security > Troubleshoot. Then select the Windows Update troubleshooter and run it. Restart the system.

You can also try to run Microsoft’s Online Windows Update Troubleshooter and check if that is any help in fixing any of your issues.

2] Delete Temporary files

Run Disk Cleanup Tool and clear all temporary files including Browser cache & cookies.

3] Rename the Software Distribution folder

The Software Distribution folder stores files crucial to the Windows Update process. Deleting or renaming the Software Distribution folder, and restarting the system would help in replacing these files. Basically, the files get downloaded again when we restart the system.

Date: February 20, 2019 Tags: Windows Updates

How to update Windows 11 manually

Handler CBS called Error with 0x800f0816 – Windows Update error

How to fix Windows Update error 0x80242016

[email protected]

Karan Khanna is a passionate Windows user who loves troubleshooting Windows 11/10 problems in specific and writing about Microsoft technologies in general.

Источник

80244007 windows update 2012r2

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

One new install, one previous install, two different servers (server 2008 r2) full updates, WSUS 3.2.7600.226

On both servers, WSUS installs and operates properly until I try to have a client update from one of those servers, I am met with Windows update Error code 80244007 which I found to be some SOAP error, so I check the windowsupdate.log and here is the relevant part

(removed server names)

When I try to access

I am met with the error seen here

Any help would be greatly appreciated

Answers

2011-06-08 11:10:21:892 1076 ab0 PT Initializing simple targeting cookie, clientId = 28dc3c16-ed92-49bb-93ed-f9b3cf5a7b23,
target group = dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1
uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBh
dzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26Z
qQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0
GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlh
XXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg,
DNS name = computername.domain

Talk to me about how you created your WSUS Target Groups, how you configured the server to manage groups, and how you configured the machines to be assigned to a target group.

The fundamental problem here is your Target Group name is invalid.

Источник

80244007 windows update 2012r2

Сообщения: 417
Благодарности: 4

Результат выполнения команд

C:Windowssystem32>net stop wuauserv
Служба «Центр обновления Windows» останавливается.
Служба «Центр обновления Windows» успешно остановлена.
C:Windowssystem32>reg Delete HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdate /v PingID /f
Ошибка: Не удается найти указанный раздел или параметр в реестре.
C:Windowssystem32>reg Delete HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdate /v AccountDomainSid /f
Ошибка: Не удается найти указанный раздел или параметр в реестре.
C:Windowssystem32>reg Delete HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdate /v SusClientId /f
Операция успешно завершена.
C:Windowssystem32>reg Delete HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdate /v SusClientIDValidation /f
Операция успешно завершена.
C:Windowssystem32>net start wuauserv
Служба «Центр обновления Windows» запускается.
Служба «Центр обновления Windows» успешно запущена.
C:Windowssystem32>wuauclt.exe /resetauthorization /detectnow
C:Windowssystem32>

Запросил обновления, та же самая ошибка

• Обновление функций до Windows 10 Pro, версия 1607, ru-ru, розничная лицензия — ошибка 0x80244007

— Переименовывал softwaredistribution
— удалял все из папки download
— ну и соответственно гуглил ошибку
— загрузку esd файлов включил, иис перезапускал
Все предлагаемы KB для решения проблемы имеют один результат «Обновления не применимы к вашему компьютеру»
Ссылка на вашу страницу пишет. что страница не существует

Сообщения: 417
Благодарности: 4

В компонентах сервера во framework 4.5 включил функцию «Активация HTTP»

Теперь ошибка стала 0xc1800118

Погуглив это из за того что клиетская винда не может расшифровать загруженное КБ

Скачав обновление KB2919355 сервер пишет, что оно установлена.

Может есть более новое обн

Сообщения: 36075
Благодарности: 6523

Сообщения: 417
Благодарности: 4

Установил менеджемент студио на ВСУС
В окне подключения указываю имя сервера \.pipeMICROSOFT##WIDtsqlquery
Получаю ошибку

Ошибка входа пользователя «MGorNV». (.Net SqlClient Data Provider)

——————————
Имя сервера: \.pipeMICROSOFT##WIDtsqlquery
Номер ошибки: 18456
Серьезность: 14
Состояние: 1
Номер строки: 65536

в System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
в System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
в System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
в System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
в System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
в System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
в System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
в System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
в System.Data.SqlClient.SqlConnection.Open()
в Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnect ionInfo ci, IServerType server)
в Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Где ошибка закралась?

» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″> » width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>

Сообщения: 417
Благодарности: 4

По предположениям: не повышалась версия потому, что обновления на ПК версии 1609 пришли раньше чем на WSUS было установлено обновление, которое вместе с обновление отправлял ключ дешифровки обновления для повышения до версии 1609. Поэтому надо отклонить и удалить все обновления до 1609, установить нужное КБ на сервер и заново загрузить обновления для 1609.

Источник