If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Windows 10 1809 Problems W/Windows Defender
Running WIndows 10 Pro 32 bit. Had x86 and x64 computers undated to 1809.
Have a problem with the WIndows Pro 32 bit laptop. WIndows Defender does not run and has a message "Engine Unavailable." I believe the fact the BITS service also will not work is probably the main problem. The following is some of the info contained in the Event Viewer. The Background Intelligent Transfer Service service terminated with the following service-specific error: %%2388526088 The BITS service failed to start. Error 0x8E5E0408. The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Installation Failu Windows failed to install the following update with error 0x80070643: Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.764.0). I have spent hours on this trying to get BITS to work will take any suggestions of how the solve this I can get. Will provide any additional information requested. -- Bill Brought to you from Anchorage, Alaska |
Ads |
#2
|
|||
|
|||
Windows 10 1809 Problems W/Windows Defender
On 12/16/2018 5:39 PM, Bill Bradshaw wrote:
Running WIndows 10 Pro 32 bit. Had x86 and x64 computers undated to 1809. Have a problem with the WIndows Pro 32 bit laptop. WIndows Defender does not run and has a message "Engine Unavailable." I believe the fact the BITS service also will not work is probably the main problem. The following is some of the info contained in the Event Viewer. The Background Intelligent Transfer Service service terminated with the following service-specific error: %%2388526088 The BITS service failed to start. Error 0x8E5E0408. The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Installation Failu Windows failed to install the following update with error 0x80070643: Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.764.0). I have spent hours on this trying to get BITS to work will take any suggestions of how the solve this I can get. Will provide any additional information requested. Try defecating in Donald Trump's mouth and see if that fixes it. |
#3
|
|||
|
|||
Windows 10 1809 Problems W/Windows Defender
Idaho Homo Joe wrote:
On 12/16/2018 5:39 PM, Bill Bradshaw wrote: Running WIndows 10 Pro 32 bit. Had x86 and x64 computers undated to 1809. Have a problem with the WIndows Pro 32 bit laptop. WIndows Defender does not run and has a message "Engine Unavailable." I believe the fact the BITS service also will not work is probably the main problem. The following is some of the info contained in the Event Viewer. The Background Intelligent Transfer Service service terminated with the following service-specific error: %%2388526088 The BITS service failed to start. Error 0x8E5E0408. The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Installation Failu Windows failed to install the following update with error 0x80070643: Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.764.0). I have spent hours on this trying to get BITS to work will take any suggestions of how the solve this I can get. Will provide any additional information requested. Try defecating I think that's the method the Microsoft Troubleshooter uses. I tried running that error number 0x8E5E0408, and boy, what a mess. Decimal 2388526088 is the same thing as hex 0x8E5E0408. No single thread yet has hinted at a root cause. A lot of the threads, I can't even match exactly to the info above. (Some of the 0x8E5E0408 ones are associated with a Windows Store issue.) BITS and QMgr work together. This seems to correspond to the 17134 on the test stand right now. https://social.technet.microsoft.com...=winserverwsus Stop the BITS service, delete any data files under ProgramData\Microsoft\Network\Downloader, and reboot. The files in that Downloader folder are an ESE Jet Blue database. I have a folder by that name, and it's the only Network\Downloader on the machine right now. Yet, if we look at the Windows Update reset script here, the files are in a different place. People use this expecting to properly reset Windows Update. Yet the ProgramData folder isn't mentioned at all. https://www.tenforums.com/tutorials/...dows-10-a.html :Reset del /s /q /f "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" del /s /q /f "%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qm gr*.dat" When I look with nfi.exe at the C: of 17134.471 release, I'm not seeing any "Network\Downloader" entries except the ProgramData one. Some posters are getting that error while working with Windows Store, and their "cure" involves logging in with a different account for some reason. Whereas your situation somehow involves Windows Update. (Windows Store can be reset with "wsreset", but I doubt it does more than just the ws side of things.) Note that, the last check I did on a machine here (the actual reason for installing that 17134), is to test the switchover of Delivery Optimization "dosvc" back to using BITS, as BITS doesn't seem to be used for as much as it once was. It's possible for example, that fixing BITS isn't the end of any trouble. I don't know now, at the moment, what the responsibility split is between BITS and dosvc (Delivery Optimization, which can be switched off partially in the Settings wheel, and completely shut off in GPEdit as a setting of 100=Bypass). Um, pick your poison I guess. Maybe Idaho was right. Paul |
#4
|
|||
|
|||
Windows 10 1809 Problems W/Windows Defender
Paul wrote:
Idaho Homo Joe wrote: On 12/16/2018 5:39 PM, Bill Bradshaw wrote: Running WIndows 10 Pro 32 bit. Had x86 and x64 computers undated to 1809. Have a problem with the WIndows Pro 32 bit laptop. WIndows Defender does not run and has a message "Engine Unavailable." I believe the fact the BITS service also will not work is probably the main problem. The following is some of the info contained in the Event Viewer. The Background Intelligent Transfer Service service terminated with the following service-specific error: %%2388526088 The BITS service failed to start. Error 0x8E5E0408. The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Installation Failu Windows failed to install the following update with error 0x80070643: Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.764.0). I have spent hours on this trying to get BITS to work will take any suggestions of how the solve this I can get. Will provide any additional information requested. Try defecating I think that's the method the Microsoft Troubleshooter uses. I tried running that error number 0x8E5E0408, and boy, what a mess. Decimal 2388526088 is the same thing as hex 0x8E5E0408. No single thread yet has hinted at a root cause. A lot of the threads, I can't even match exactly to the info above. (Some of the 0x8E5E0408 ones are associated with a Windows Store issue.) BITS and QMgr work together. This seems to correspond to the 17134 on the test stand right now. https://social.technet.microsoft.com...=winserverwsus Stop the BITS service, delete any data files under ProgramData\Microsoft\Network\Downloader, and reboot. The files in that Downloader folder are an ESE Jet Blue database. I have a folder by that name, and it's the only Network\Downloader on the machine right now. Yet, if we look at the Windows Update reset script here, the files are in a different place. People use this expecting to properly reset Windows Update. Yet the ProgramData folder isn't mentioned at all. https://www.tenforums.com/tutorials/...dows-10-a.html Reset del /s /q /f "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" del /s /q /f "%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qm gr*.dat" When I look with nfi.exe at the C: of 17134.471 release, I'm not seeing any "Network\Downloader" entries except the ProgramData one. Some posters are getting that error while working with Windows Store, and their "cure" involves logging in with a different account for some reason. Whereas your situation somehow involves Windows Update. (Windows Store can be reset with "wsreset", but I doubt it does more than just the ws side of things.) Note that, the last check I did on a machine here (the actual reason for installing that 17134), is to test the switchover of Delivery Optimization "dosvc" back to using BITS, as BITS doesn't seem to be used for as much as it once was. It's possible for example, that fixing BITS isn't the end of any trouble. I don't know now, at the moment, what the responsibility split is between BITS and dosvc (Delivery Optimization, which can be switched off partially in the Settings wheel, and completely shut off in GPEdit as a setting of 100=Bypass). Um, pick your poison I guess. Maybe Idaho was right. Paul I gave up and went back to 1803. Fortunately I partition my harddrives so when I have to fool with the operating system it only involves the C partition and I keep current backups. Bill |
Thread Tools | |
Display Modes | Rate This Thread |
|
|