- This topic has 26 replies, 4 voices, and was last updated 8 years, 1 month ago by .
-
Posts
-
Recently did clean installs of Windows 10 on a number of laptops.
Some Lenovo Yoga2Pro.
Some HP tc4400 (quite old but running just fine).
All the Yoga’s but non of the HP’s get this error when trying to perform windows update with BatchPatch:
10:00:41> Windows Update: Error: -1073741819. HRESULT: -2147024894. Could not find file ‘\yoga2projbC$Program FilesBatchPatchBatchPatchTempResult.log’.
10:00:30> Windows Update: Executing BatchPatchRemoteAgent.exe…
10:00:29> Windows Update: Attempting to initiate Windows Update (Action: Download and install updates. Server selection: Default / Managed) …
10:00:29> Windows Update: Establishing connection…
10:00:29> Windows Update: Initializing…
10:00:29> Windows Update: Queued… (Download and install updates + reboot if required)
I can access this folder on the target from the host and I can run psexec commands on the target from the host.
The fact that it happens on the Lenovo’s but not the HP’s makes me suspect an issue with a Lenovo-specific driver or utility (which are limited to those detected and installed by a clean Windows 10 install).
Please try running Windows Update manually on the target computer (*without* using BatchPatch). Do you encounter the same error when using Windows Update manually? This might not be a BatchPatch issue at all.
-Doug
I have this same Error when trying to update Windows 10 Boxes. I am fully updated and can get BatchPatch to work on just about every other feature except check / run updates… However this is the Error I get.
And what happens when you try to use/run Windows Update manually on the target computer WITHOUT using BatchPatch? Does Windows Update work normally or does it throw the same (or different) error too?
When I run update manually it runs perfectly. Could it be the commands / location of Windows Update is Different in Windows 10 and batchpatch does not support it?
Thanks for confirming. We have plenty of other users using Windows 10 without issue. Additionally, we have no issues using Windows 10 in our lab. That said, at the moment I’m not quite sure what the issue is that you’re encountering. I will email you to troubleshoot further.
-Doug
msuskin confirmed that this turned out to be a WSUS issue in his environment.
-Doug
It’s certainly peculiar that you only experience this issue on your Lenova Yoga2Pro devices. I agree with your assessment that it seems like it would be something related to Lenovo specific drivers or applications. Coincidentally there was recently a bit of security related news regarding Lenovo practices, where essentially it was discovered that they are using some technology to have the BIOS download/install/inject their own utilities even when performing a clean installation of Windows. It’s the “Lenovo Service Engine” (LSE), and it sounds like this could definitely be your culprit. And so now they have said “Lenovo’s use of LSE was not consistent with Microsoft’s guidelines. As a result, LSE is no longer being installed on Lenovo systems. It is strongly recommended that customers update their systems with the new BIOS firmware which disables and/or removes this feature.”
Here is just one of many articles on the subject:
If I were you I would update the BIOS on one of the Lenovo systems and then do a fresh install of Windows 10 and see what happens then. I have a feeling all will work fine for you then.
Keep me posted.
Thanks,
Doug
To *really* know for sure I would still install the OS from scratch on the updated system. Aside from that, unfortunately I don’t have any other suggestions at the moment since I’m not able to reproduce your issue, and it seems to be related to a specific hardware type, which is peculiar, as you’ve noted since the problem is occurring/manifesting in software, not hardware. I believe the problem is software-related, not hardware, but your guess is as good as mine right now since you have the actual systems in front of you. It certainly doesn’t make much sense that the same OS could be installed on two different systems, but then the systems behave differently. This does imply, as you originally stated, that the issue might be related to hardware specific drivers or applications. However, it’s nearly impossible at the moment for me to guess at what, specifically, is making the problems occur. I’ll think on this some more.
-Doug
Another user who was experiencing this error determined that the source of the problem was his WSUS server:
I’m having also the problem with two Hyper-V Based Windows 10 (Virtual Maschines). Each time when I start the Batchpatch Windows Update I’m getting the -2147024894 Error Message.
Both of them where installed with the new 1511 build directly. Tried already to delete the SoftwareDistribution Folder but the same error appears again.
I checkt the update manualy on both clients. Its working corectly with the wsus server, just with the batchpach it doesn’t work.
Who can help me to fix that Problem?
best regards
Andreas
Andreas – first we need to confirm please what is the complete error message that you are seeing? The topic of this post is “Error: -1073741819. HRESULT: -2147024894.”
You mentioned -2147024894, but that is only one piece of the error message, and it’s the least important part. We need the entire error message please. There should be two different error numbers, with the first number being the most important.
Thanks,
Doug
Hey Doug,
the full error message is like that:
Error: -1073741819. HRESULT: -2147024894. Could not find file ‘\MyComputerC$Program FilesBatchPatchBatchPatchTempResult.log’.
Thanks for confirming. The next would be to examine your WindowsUpdate.log on that machine to see what it reveals. We should see an error in the log. Also, have a look at this posting, which explains the resolution that a couple of people used for this issue.
Windows Update: Error: -1073741819. HRESULT: -2147024894.
-Doug
my issuse is espcialy related with windows 10 only and batchpatch. If i going to run windows update manually on the maschines it works great. Here is a update request with batchpatch (the WindowsUpdateLog from the target machine Windows 10 Enterprise):
2016.03.03 11:08:50.0937042 1104 4148 Shared * START * Service startup
2016.03.03 11:08:50.1190716 1104 4148 Agent WU client version 10.0.10586.103
2016.03.03 11:08:50.1196322 1104 4148 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2016.03.03 11:08:50.1198505 1104 4148 Agent Base directory: C:windowsSoftwareDistribution
2016.03.03 11:08:50.1200252 1104 4148 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2016.03.03 11:08:50.1200779 1104 4148 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016.03.03 11:08:50.1212009 1104 4148 Shared Network state: Connected
2016.03.03 11:08:50.1305835 1104 4148 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2016.03.03 11:08:50.1306036 1104 4148 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016.03.03 11:08:50.1306178 1104 4148 Shared Power status changed
2016.03.03 11:08:50.1718807 1104 4148 Agent Initializing global settings cache
2016.03.03 11:08:50.1718825 1104 4148 Agent WSUS server: https://MyWSUS.DOMAIN.CH:443
2016.03.03 11:08:50.1718836 1104 4148 Agent WSUS status server: https://MyWSUS.DOMAIN.CH:443
2016.03.03 11:08:50.1718842 1104 4148 Agent Target group: Codx-Clients-Win10
2016.03.03 11:08:50.1718850 1104 4148 Agent Windows Update access disabled: No
2016.03.03 11:08:50.1722177 1104 2008 Agent Timer: 855E8A7C-ECB4-4CA3-B045-1DFA50104289, Expires 2016-03-03 10:23:22, not idle-only, <NULL>network-only
2016.03.03 11:08:50.1722339 1104 2008 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-03-04 07:35:13, not idle-only, not network-only
2016.03.03 11:08:50.1879862 1104 2008 Agent Initializing Windows Update Agent
2016.03.03 11:08:50.1881477 1104 2008 DownloadManager Download manager restoring 0 downloads
2016.03.03 11:08:50.1882691 1104 2008 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2016.03.03 11:08:50.3674396 1104 2008 Agent * START * Queueing Finding updates [CallerId = BatchPatch Id = 1]
2016.03.03 11:08:50.3674579 1104 2008 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2016.03.03 11:08:50.3681940 6648 5800 ComApi Search ClientId = BatchPatch
2016.03.03 11:08:50.3691814 1104 1516 Agent * END * Queueing Finding updates [CallerId = BatchPatch Id = 1]
2016.03.03 11:08:50.3699747 1104 1516 Agent * START * Finding updates CallerId = BatchPatch Id = 1
2016.03.03 11:08:50.3699763 1104 1516 Agent Online = Yes; Ignore download priority = No
2016.03.03 11:08:50.3699773 1104 1516 Agent Criteria = IsInstalled=0 and Type=’Software’ and IsHidden=0″”
2016.03.03 11:08:50.3699829 1104 1516 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016.03.03 11:08:50.3699838 1104 1516 Agent Search Scope = {Machine}
2016.03.03 11:08:50.3699887 1104 1516 Agent Caller SID for Applicability: S-1-5-18
2016.03.03 11:08:50.3699899 1104 1516 Agent RegisterService is set
2016.03.03 11:08:50.3712386 1104 1516 Misc Got WSUS Client/Server URL: https://MyWSUS.DOMAIN.CH:443/ClientWebService/client.asmx””
2016.03.03 11:08:50.3733448 1104 6372 DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2016.03.03 11:08:50.3914270 1104 6372 DownloadManager PurgeExpiredUpdates::Found 298 non expired updates.
2016.03.03 11:08:50.4939325 1104 6372 DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
2016.03.03 11:08:50.4951073 1104 6372 Shared Effective power state: AC
2016.03.03 11:08:50.4951097 1104 6372 DownloadManager Power state change detected. Source now: AC
2016.03.03 11:08:51.1740334 1104 1516 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://MyWSUS.DOMAIN.CH:443/ClientWebService/client.asmx
2016.03.03 11:08:51.1740481 1104 1516 ProtocolTalker OK to reuse existing configuration
2016.03.03 11:08:51.1740565 1104 1516 ProtocolTalker Existing cookie is valid, just use it
2016.03.03 11:08:51.1740673 1104 1516 ProtocolTalker PTInfo: Server requested registration
2016.03.03 11:08:54.4581303 1104 1516 WebServices Auto proxy settings for this web service call.
2016.03.03 11:08:54.6074717 1104 1516 ProtocolTalker PTInfo: syncing with server using normal query
2016.03.03 11:08:54.6188786 1104 1516 ProtocolTalker PopulateDataStore failed 0x8024000e
2016.03.03 11:08:54.6188985 1104 1516 ProtocolTalker SyncUpdates round trips: 2
2016.03.03 11:08:54.6188993 1104 1516 ProtocolTalker Sync of Drivers failed (Software succeeded) 0x8024000e
2016.03.03 11:08:57.2841052 1104 1516 Agent Added update D079382E-82C6-4544-8BBF-0D13C22E6E95.200 to search result
2016.03.03 11:08:57.2841200 1104 1516 Agent Added update B6392B54-852D-43F4-828C-2376EAA3C67F.200 to search result
2016.03.03 11:08:57.2841535 1104 1516 Agent Found 2 updates and 92 categories in search; evaluated appl. rules of 995 out of 1663 deployed entities
2016.03.03 11:08:57.2947532 1104 1516 Agent Reporting status event with 0 installable, 70 installed, 0 installed pending, 0 failed and 2 downloaded updates
2016.03.03 11:08:57.2960135 1104 1516 Agent * END * Finding updates CallerId = BatchPatch Id = 1
2016.03.03 11:08:57.2988291 6648 3700 ComApi *RESUMED* Search ClientId = BatchPatch
2016.03.03 11:08:57.3484720 6648 3700 ComApi Updates found = 2
2016.03.03 11:08:57.3484755 6648 3700 ComApi * END * Search ClientId = BatchPatch
2016.03.03 11:08:57.3514384 6648 5800 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
I guess the point is the PopulateDataStore failed but I couldn’t find why this coming up. Ah another wired thing is, if the client doesn’t need to install any update, than batchpatch works and report that there is no update available but as soon as there is a update that needs to be installed, it doesn’t work anymore. Really wired. Can you help me with that?
Hi Andreas – I understand the issue. To be clear, the symptoms are as follows:
-BatchPatch works fine/normally on all targets except for Win 10 targets
-When checking for Windows Updates on Win 10 targets manually using the control panel Windows Update GUI, the check works properly
-When checking for Windows Updates on Win 10 targets using BatchPatch when the Win 10 targets are pointing to a WSUS server, the Error: -1073741819. HRESULT: -2147024894 occurs.
-When checking for Windows Updates on Win 10 targets using BatchPatch when BatchPatch is configured to bypass the local WSUS server and search instead on ‘Windows Update’ or ‘Microsoft Update,’ the check works properly.
We have had several customers report this problem. I was able to obtain a copy of the WSUS database of one such customer, and then we were able to reproduce the problem here. We were able to isolate the cause as being invalid result data returned from the search for updates against the WSUS.
-2145124338 => 0x8024000E WU_E_XML_INVALID Windows Update Agent found invalid information in the update’s XML data.
In the 20160304 version of BatchPatch we were able to add additional error handling so that in the future when this error occurs we will see it reported properly as -2145124338. The issue appears to be caused by having one or more corrupt updates (most likely driver updates) in the WSUS database.
There are several options for resolution:
Option 0: Run the WSUS Server Cleanup Wizard (in the WSUS console select ‘Options > Server Cleanup Wizard.’ This cleanup routine may or may not fix the issue, but it is likely worth trying as a first step.
Option 1: After a lot of testing with one customer’s database, we were able to determine the culprit update in his database to be ‘AMD driver update for Pci Bus’ I was able to decline this single update and then wait a few minutes, and the error disappeared. For whatever reason, after declining the update SQL still has to do some processing before the error stopped occurring, so make sure to give it some time if the error doesn’t immediately disappear.
Option 2: Selectively decline all of the updates in the ‘Windows 10 and later drivers’ group. To do this…
A. create a new update view on the WSUS by right-clicking on ‘Updates’ in the left-pane, and selecting the option for ‘New Update View…’
B. Check the box ‘Updates are for a specific product.’
C. Modify the checkbox list of products to include ONLY the checkbox for ‘Windows 10 and later drivers.’
D. Specify a name for the view called ‘Windows 10 and later drivers’ or whatever you prefer and click OK.
E. Now make sure the new ‘Windows 10 and later drivers’ view that you just created is the selected view.
F. Change the the filter drop-downs to show
Approval: 'Any Except Declined' Status: 'Any'G. Select all updates even if they are not approved, and go ahead and decline them. After the updates are declined you might still need to wait a few minutes (or longer) before the error will stop occurring.
Option 3: Rebuild the WSUS database. Fortunately, it only takes about 30 minutes to install and configure WSUS, so this is not a painful process. Less than ideal, yes. However, in most cases it is probably quicker and easier than the 4th option.
Option 4: Find the problematic update and decline it. The problem with this approach is that we do not have a way to determine which update is the source of the problem without very painstaking testing. At the time of this writing we only know of 4 users who have been affected by this problem. We do not know if the same update was the culprit for each user, but we do know that at least 2 of the users the issue was a driver update, and I believe there is a good chance that in all cases it might be the very same ‘AMD driver update for Pci Bus’ mentioned in option 1. If you find that to be the case, please post in this thread to let us know.
When we release the new version of BP (EDIT: this new version was released 2016-03-04) I’d like for you to confirm that you begin seeing the error reported as -2145124338, which will confirm that the error you are experiencing is, in fact, the same as the error that we were able to reproduce with another customer’s WSUS database. If you end up receiving a different error, I’d like to know what that is.
In BatchPatch ‘All Messages’ column it will be reported as:
DATETIME> Windows Update: Error 1611: -106. Failure
DATETIME> Windows Update: -106G: Update search completed with errors: -2145124338
Thanks,
Doug
Hey Doug,
thanks a lot for your answer. I could fixe my wsus again like you said. Reinstalled everthing and I approved just the basic Windows 10 updates. Now I’m going ahead, with approving also feature updates and drives and I will see when it stops to work again.
The symptoms that you descripted, i can confirm that its exactly what it is also in my case. I will update this post again as soon as I’ve more information
Thanks, Andreas. Yes, please let me know if you run into this problem again in the future. I don’t think it’s likely that it will occur again, but you never know. We have a lot of customers using the software with Windows 10 and with no problems at all. Additionally, in our lab, we have never experienced the issue. That said, it’s unclear why the issue has occurred for the few customers who have posted to this thread, including yourself.
-Doug
Error 1611: 1072. Failure
ERROR_SERVICE_MARKED_FOR_DELETE
1072 (0x430)
The specified service has been marked for deletion.
I have never seen this reported by BatchPatch. I suspect that Windows is talking about the PsExec service (PSEXESVC) in this instance having been marked for deletion. You could probably confirm that by trying to execute psexec at the command line against that machine. So for example you could run something like:
psexec \targetComputer IPCONFIGTo resolve the problem my guess is that if you simply reboot the machine(s) in question, when it/they come back up after reboot it/they will behave normally. Let me know how it goes.
-Doug
hey doug,
after reinstalling the WSUS it was working fine. As soon as I select in the product catorgy of WSUS the “Windows 10 and later drivers”, the error appears again (of course after a successfull download from microsoft for my wsus). So the problem seems to be with a driver package (only for Windows 10!), I also approved all the drivers for install but I think this stept doesn’t matter. I declined all the drivers again and did the WSUS cleanup, now all my Windows 10 clients are back to work again with my WSUS Server. This is just for your information and I’m looking for the new BP Version hoppfully with a fix for this problem 😉
– Andreas
Andreas – Thank you for this information! It’s very helpful to know that the issue is/was specifically related to a driver package for Win 10.
However, unfortunately at the moment this does not appear to be something that we can “fix” per se. The issue is not in BatchPatch. The issue is that a corrupt search result is being returned by the WSUS server, and we are not able to process/parse this corrupt search result. At this time we simply do not have a way to code around the problem. The only solution at present is to fix the issue on the WSUS side. If this changes at any time, I will post more info to this thread.
Thanks again,
Doug
After a lot of testing with one customer’s database, we were able to determine the culprit update in his database to be ‘AMD driver update for Pci Bus’ I was able to decline this single update and then wait a few minutes, and the error disappeared.
-Doug
- You must be logged in to reply to this topic.