Windows 10: Cum Update 2018-02 causes multiple Powershell crashes

Discus and support Cum Update 2018-02 causes multiple Powershell crashes in Windows 10 Updates and Activation to solve the problem; A friend has had nearly 3000 Powershell crashes logged ever since build 16299.248 was installed. Powershell crashes spontaneously, possibly when a... Discussion in 'Windows 10 Updates and Activation' started by spilly, Mar 23, 2018.

  1. spilly Win User

    Cum Update 2018-02 causes multiple Powershell crashes


    A friend has had nearly 3000 Powershell crashes logged ever since build 16299.248 was installed.
    Powershell crashes spontaneously, possibly when a background task starts. I believe build 248 has introduced a new bug.

    Q1) Does anyone have a suggestion of the cause or how to make the system more usable? (logs attached)
    Q2) Should I report this as a bug? If so, where and how?
    Q3) Do I just have to wait and hope MS will fix this in a future WU package?

    Details: Each crash causes an on-top error window "Powershell has stopped working", which has to be closed manually.
    If PC is left idling, on resuming there can be a stack of 10 or 20 such windows to close.
    I'm pretty sure KB4074588 build 248 is responsible. If build is 248 or higher, new error windows happen spontaneously throughout the session; with build 192, no error windows occur.
    As this is W10 Home, WU promptly re-installs the full current Cum Update, with a pending restart to complete the installation, so we can't escape the hassle. (The actual user is relatively inexperienced.)
    Prior to 2018-02 there were no problems of this kind.

    The system is used for email, browsing, MS Office and Skype.
    System: Win 10 Home 64bit on Dell Inspiron 17R 5720, Intel Core i5-3210M CPU @ 2.50GHz, 6GB RAM, 1x1TB HDD for data + 1x120GB mSATA SSD as system disk; integrated Intel HD Graphics 4000


    Actions taken: I googled, but didn't find any similar PowerShell crash cases; Ran Mem test; CHKDSK C: /F /R; SFC /scannow; DISM /Online /Cleanup-Image /RestoreHealth - all passed OK.
    Uninstalling Cum Updates back to build 16299.192 seems to fix the problem; Reinstalling any Update after build 192 brings it back immediately.

    Attached Documentation: Zip containing
    1) Event log (< 40 events logged), from restart to first error window
    2) Contents of %ProgFiles% WER folder related to this same error


    NB I posted this issue in General Maintenance here a couple of days ago, before I discovered this is a Windows Update issue. Is there a way I can move my thread to a better forum if I've posted to the wrong one?

    :)
     
    spilly, Mar 23, 2018
    #1
  2. Sumit Dhiman2, Mar 23, 2018
    #2
  3. The windows 10 fall upgrade 1709 fails after about 45% mark.. Then gives an error message and returns system to 1703

    Look at the setupact.log at these times for context.

    The following is the second error referring to disk space.

    Note... I have 200 gb going into the update...

    There are no disk problems.. ran a chkdsk /f

    no issues??

    2018-02-05 19:55:23, Info SP ==- DUUpdateInfo -======================================

    2018-02-05 19:55:23, Info SP Search succeeded; will skip subsequent attempts.

    2018-02-05 19:55:23, Info SP Update 990c343c-6587-4544-99fd-fc1990205a72: maximum download size [535912371] bytes, recommended hard disk space [2005] MB

    2018-02-05 19:55:23, Info SP Update 0ce6f337-8c7f-49cd-8c75-e1488a4cd8da: maximum download size [726767] bytes, recommended hard disk space [0] MB

    2018-02-05 19:55:23, Info SP Component update 0ce6f337-8c7f-49cd-8c75-e1488a4cd8da will not be extracted; we'll estimate the recommended hard disk space at [6] MB

    2018-02-05 19:55:23, Warning SP Inconsistencies found in recommended hard disk space; will not use it

    2018-02-05 19:55:23, Info SP DU disk space checkpoint before download:

    2018-02-05 19:55:23, Info SP Available: 192300883968

    2018-02-05 19:55:23, Info SP Needed by download of updates: 1073278276

    2018-02-05 19:55:23, Info SP Needed by setup: 597688320

    2018-02-05 19:55:23, Info SP Download attempt 1 of 1

    2018-02-05 19:55:23, Info SP Downloading dynamic updates

    2018-02-05 19:55:23, Info SP Skipping on metered networks

    2018-02-05 19:55:23, Info DU DU::CDUSession:Cum Update 2018-02 causes multiple Powershell crashes :Download: Beginning asynchronous download

    2018-02-05 19:55:23, Info DU DU::CDUSession:Cum Update 2018-02 causes multiple Powershell crashes :Download: Ending asynchronous download

    2018-02-05 19:55:33, Info MOUPG Action progress: [11%]

    2018-02-05 19:55:40, Info MOUPG Action progress: [12%]

    2018-02-05 19:55:49, Info MOUPG Action progress: [13%]

    2018-02-05 19:55:56, Info MOUPG Action progress: [14%]

    2018-02-05 19:56:05, Info MOUPG Action progress: [15%]

    2018-02-05 19:56:12, Info MOUPG Action progress: [16%]

    2018-02-05 19:56:37, Info SP Updates downloaded successfully

    2018-02-05 19:56:37, Info SP Download succeeded; will skip subsequent attempts.

    2018-02-05 19:56:42, Info SP Successfully moved update 990c343c-6587-4544-99fd-fc1990205a72 to C:\$WINDOWS.~BT\GDRs\DU\990c343c-6587-4544-99fd-fc1990205a72

    2018-02-05 19:56:42, Info SP Successfully moved update 0ce6f337-8c7f-49cd-8c75-e1488a4cd8da to C:\$WINDOWS.~BT\GDRs\DU\0ce6f337-8c7f-49cd-8c75-e1488a4cd8da

    2018-02-05 19:56:42, Error SP CDownloadDUUpdates:Cum Update 2018-02 causes multiple Powershell crashes :DoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff

    2018-02-05 19:56:42, Error SP CSetupPlatform:Cum Update 2018-02 causes multiple Powershell crashes :DownloadDynamicUpdates: Failed to download updates. Error: 0x8000FFFF

    2018-02-05 19:56:42, Error MOUPG DUImage: Failed to execute GDR search and download [0x8000ffff]

    2018-02-05 19:56:42, Info MOUPG DUImage: Searching for driver updates...

    2018-02-05 19:56:43, Info MOUPG Action progress: [20%]

    2018-02-05 19:56:43, Info MOUPG Task progress: [52%]

    2018-02-05 19:56:43, Info MOUPG Overall progress: [28%]

    2018-02-05 19:56:43, Info MOUPG Mapped Global progress: [28%]

    2018-02-05 19:57:41, Info SP OPERATIONTRACK: Enqueue Operation: 13|Download Driver Dynamic Updates

    2018-02-05 19:57:41, Info SP DU Client Application Information

    2018-02-05 19:57:41, Info SP ID = SetupHost.exe

    2018-02-05 19:57:41, Info SP Architecture = 9

    2018-02-05 19:57:41, Info SP Major Version = 10

    2018-02-05 19:57:41, Info SP Minor Version = 0

    2018-02-05 19:57:41, Info SP Build = 16299

    2018-02-05 19:57:41, Info SP SP Build = 15

    2018-02-05 19:57:41, Info SP SP Level = 0

    2018-02-05 19:57:41, Info SP Branch = rs3_release

    2018-02-05 19:57:41, Info SP SPInitializeDU: DU has already been initialized; proceeding.

    2018-02-05 19:57:41, Info SP Executing download operation: Download Driver Dynamic Updates

    2018-02-05 19:57:41, Info SP DU Image Information

    2018-02-05 19:57:41, Info SP Architecture = 9

    2018-02-05 19:57:41, Info SP Edition ID = Professional

    2018-02-05 19:57:41, Info SP Installation Type = Client

    2018-02-05 19:57:41, Info SP Language = en-US

    2018-02-05 19:57:41, Info SP Major Version = 10

    2018-02-05 19:57:41, Info SP Minor Version = 0

    2018-02-05 19:57:41, Info SP Build = 16299

    2018-02-05 19:57:41, Info SP SP Build = 15

    2018-02-05 19:57:41, Info SP SP Level = 0

    2018-02-05 19:57:41, Info SP Branch = rs3_release

    2018-02-05 19:57:41, Info SP GDR DU Revision = 0

    2018-02-05 19:57:41, Info SP Scanning for driver updates; will optimize first search attempt.

    2018-02-05 19:57:41, Info SP Search attempt 1 of 5

    2018-02-05 19:57:41, Info SP Searching for dynamic updates

    2018-02-05 19:57:41, Info SP Update types:

    2018-02-05 19:57:41, Info SP Driver updates

    2018-02-05 19:57:41, Info SP Category IDs:

    2018-02-05 19:57:41, Info SP 405706ed-f1d7-47ea-91e1-eb8860039715

    2018-02-05 19:57:41, Info SP 34f268b4-7e2d-40e1-8966-8bb6ea3dad27

    2018-02-05 19:57:41, Info SP 0ba562e6-a6ba-490d-bdce-93a770ba8d21

    2018-02-05 19:57:41, Info SP 06da2f0c-7937-4e28-b46c-a37317eade73

    2018-02-05 19:57:41, Info SP c70f1038-66ac-443d-9e58-ac22e891e4fb

    2018-02-05 19:57:41, Info SP b7f52cfb-c9e9-4481-9bc0-c8b4e208ba39

    2018-02-05 19:57:41, Info SP Using WU driver applicability via IUpgradeInternalSession

    2018-02-05 19:57:41, Info SP Using WU driver applicability to skip existing drivers

    2018-02-05 19:57:41, Info SP Using WU caller profile search criterion

    2018-02-05 19:57:41, Info DU Got IUpdateSearcher properties: server selection = 0, service ID = 00000000-0000-0000-0000-000000000000; will restore later

    2018-02-05 19:57:41, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057

    2018-02-05 19:57:41, Warning SP pDUSearch: DUSearch failed. hr = 0x80070057

    2018-02-05 19:57:41, Info SP Search attempt 2 of 5

    2018-02-05 19:57:41, Info SP Searching for dynamic updates

    2018-02-05 19:57:41, Info SP Update types:

    2018-02-05 19:57:41, Info SP Driver updates

    2018-02-05 19:57:41, Info SP Category IDs:

    2018-02-05 19:57:41, Info SP 405706ed-f1d7-47ea-91e1-eb8860039715

    2018-02-05 19:57:41, Info SP 34f268b4-7e2d-40e1-8966-8bb6ea3dad27

    2018-02-05 19:57:41, Info SP 0ba562e6-a6ba-490d-bdce-93a770ba8d21

    2018-02-05 19:57:41, Info SP 06da2f0c-7937-4e28-b46c-a37317eade73

    2018-02-05 19:57:41, Info SP c70f1038-66ac-443d-9e58-ac22e891e4fb

    2018-02-05 19:57:41, Info SP b7f52cfb-c9e9-4481-9bc0-c8b4e208ba39

    2018-02-05 19:57:41, Info SP Using WU driver applicability via IUpgradeInternalSession

    2018-02-05 19:57:41, Info SP Using WU caller profile search criterion

    2018-02-05 19:57:41, Info DU Got IUpdateSearcher properties: server selection = 0, service ID = 00000000-0000-0000-0000-000000000000; will restore later

    2018-02-05 19:57:41, Error DU DU::CDUSession::BuildSearchCriteria: Caller profile search criterion is not supported. hr = 0x80070032

    2018-02-05 19:57:41, Error DU DU::CDUSession::Search: Failed to build the search criteria. hr = 0x80070032

    2018-02-05 19:57:41, Warning SP pDUSearch: DUSearch failed. hr = 0x80070032

    2018-02-05 19:57:41, Info SP Search attempt 3 of 5

    2018-02-05 19:57:41, Info SP Searching for dynamic updates

    2018-02-05 19:57:41, Info SP Update types:

    2018-02-05 19:57:41, Info SP Driver updates

    2018-02-05 19:57:41, Info SP Category IDs:

    2018-02-05 19:57:41, Info SP 405706ed-f1d7-47ea-91e1-eb8860039715

    2018-02-05 19:57:41, Info SP 34f268b4-7e2d-40e1-8966-8bb6ea3dad27

    2018-02-05 19:57:41, Info SP 0ba562e6-a6ba-490d-bdce-93a770ba8d21

    2018-02-05 19:57:41, Info SP 06da2f0c-7937-4e28-b46c-a37317eade73

    2018-02-05 19:57:41, Info SP c70f1038-66ac-443d-9e58-ac22e891e4fb

    2018-02-05 19:57:41, Info SP b7f52cfb-c9e9-4481-9bc0-c8b4e208ba39

    2018-02-05 19:57:41, Info SP Using WU driver applicability via IUpgradeInternalSession

    2018-02-05 19:57:41, Info DU Got IUpdateSearcher properties: server selection = 0, service ID = 00000000-0000-0000-0000-000000000000; will restore later

    2018-02-05 19:57:41, Info DU DU::CDUSession::Search: Beginning asynchronous search

    2018-02-05 19:57:41, Info DU DU::CDUSession::Search: Ending asynchronous search

    2018-02-05 19:57:43, Info SP Search finished successfully

    2018-02-05 19:57:43, Info SP 2 updates were found

    2018-02-05 19:57:43, Info SP ==- DUUpdateInfo -======================================

    2018-02-05 19:57:43, Info SP Description: This driver was provided by Microsoft for support of HP Photosmart 7200 Series

    2018-02-05 19:57:43, Info SP DU UpdateType: DriverUpdate:

    2018-02-05 19:57:43, Info SP GUID: edd0c4e5-a7e7-438e-88ff-c06e3a528c10

    2018-02-05 19:57:43, Info SP HardwareID: hpphotosmart_7200_se8fd3

    2018-02-05 19:57:43, Info SP LastDeploymentChangeTime: 12/16/2012

    2018-02-05 19:57:43, Info SP KB Article ID's: No Article's Found

    2018-02-05 19:57:43, Info SP ==- DUUpdateInfo -======================================

    2018-02-05 19:57:43, Info SP ==- DUUpdateInfo -======================================

    2018-02-05 19:57:43, Info SP Description: Brother Printers software update released in July, 2013

    2018-02-05 19:57:43, Info SP DU UpdateType: DriverUpdate:

    2018-02-05 19:57:43, Info SP GUID: eaa284b0-b531-4490-ae0b-9c99fa38dbd8

    2018-02-05 19:57:43, Info SP HardwareID: USBPRINT\BROTHERMFC-J4510DW3580

    2018-02-05 19:57:43, Info SP LastDeploymentChangeTime: 12/5/2013

    2018-02-05 19:57:43, Info SP KB Article ID's: No Article's Found

    2018-02-05 19:57:43, Info SP ==- DUUpdateInfo -======================================

    2018-02-05 19:57:43, Info SP Search succeeded; will skip subsequent attempts.

    2018-02-05 19:57:43, Info SP Attempting to filter the update collection to optimize download

    2018-02-05 19:57:43, Info SP Deciding dynamic update download on update:

    2018-02-05 19:57:43, Info SP Id: edd0c4e5-a7e7-438e-88ff-c06e3a528c10

    2018-02-05 19:57:43, Info SP Type: Driver

    2018-02-05 19:57:43, Info SP WU Class Name: Printers

    2018-02-05 19:57:43, Info SP Hardware ID: hpphotosmart_7200_se8fd3

    2018-02-05 19:57:43, Info SP Manufacturer: HP

    2018-02-05 19:57:43, Info SP Version Date: 6/21/2006

    2018-02-05 19:57:43, Info SP Opening DISM session for the source system (Online)

    2018-02-05 19:58:21, Info SP Found matching driver package in the current OS

    2018-02-05 19:58:21, Info SP Matching package: C:\Windows\System32\DriverStore\FileRepository\prnhp001.inf_amd64_081cf2b90ec9e6d5\prnhp001.inf

    2018-02-05 19:58:21, Info SP Initial decision for this update: Do not download.

    2018-02-05 19:58:21, Info SP Final decision for the update: Do not download.
     
    AndrewMcNeish, Mar 23, 2018
    #3
  4. spilly Win User

    Cum Update 2018-02 causes multiple Powershell crashes

    It turned out not to be a Windows Update issue after all, despite appearances to the contrary

    I had an excellent chat session with Microsoft help, first line and second line support.
    Finally tied the problem down to a rogue Javascript scheduled task. Disabling the task cured the problem.
    The task was associated somehow with Trusteer Rapport, but does not exist if Rapport is properly configured.
    So I have no idea how this all happened last February.
     
    spilly, Mar 26, 2018
    #4
Thema:

Cum Update 2018-02 causes multiple Powershell crashes

Loading...
  1. Cum Update 2018-02 causes multiple Powershell crashes - Similar Threads - Cum Update 2018

  2. Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02

    in Windows 10 Gaming
    Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02: Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02 https://answers.microsoft.com/en-us/windows/forum/all/retrieve-recovery-key-drive-label-desktop-5boutim/dd79fe34-a76f-4087-b3fa-e0001dcadf4b
  3. Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02

    in Windows 10 Software and Apps
    Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02: Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02 https://answers.microsoft.com/en-us/windows/forum/all/retrieve-recovery-key-drive-label-desktop-5boutim/dd79fe34-a76f-4087-b3fa-e0001dcadf4b
  4. Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02

    in Windows 10 Installation and Upgrade
    Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02: Retrieve recovery key Drive label DESKTOP-5BOUTIM OS 2018-02-02 https://answers.microsoft.com/en-us/windows/forum/all/retrieve-recovery-key-drive-label-desktop-5boutim/dd79fe34-a76f-4087-b3fa-e0001dcadf4b
  5. 02/02/2024 - Recent Windows Update has Caused System Instability

    in Windows 10 Gaming
    02/02/2024 - Recent Windows Update has Caused System Instability: My pc has lost a lot of its usability after the recent updates and I have not seen much word raised about this so I am doing it now.Hardware:Strix z790-e Wifi I Version 1801, most recent bios versionRTX 4090i9 14900k32GB DDR5 @5600 Mt/s XMPSince the recent updates, a lot of...
  6. 02/02/2024 - Recent Windows Update has Caused System Instability

    in Windows 10 Software and Apps
    02/02/2024 - Recent Windows Update has Caused System Instability: My pc has lost a lot of its usability after the recent updates and I have not seen much word raised about this so I am doing it now.Hardware:Strix z790-e Wifi I Version 1801, most recent bios versionRTX 4090i9 14900k32GB DDR5 @5600 Mt/s XMPSince the recent updates, a lot of...
  7. "ntoskrnl.exe" causing multiple BSOD crashes

    in Windows 10 BSOD Crashes and Debugging
    "ntoskrnl.exe" causing multiple BSOD crashes: I created a log as instructed. I'm using Windows 10 version 20H2 version 19042.868 on a Dell Inspiron 15 7000 Gaming. Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz 2.80 GHz processor, 8 gigabytes of Ram. I get a BSOD at least once a day. Most commonly, it's...
  8. Update caused crash

    in Windows 10 Installation and Upgrade
    Update caused crash: This afternoon, I sat down to work on the PC, and found it was updating. I've never encountered afternoon updates before, but waited for completion. When it was done, the screen remained black, and there was a series of four loud tones, then four lower tones. Then it...
  9. Windows Update Caused PC Crash December 17th 2018

    in Windows 10 Installation and Upgrade
    Windows Update Caused PC Crash December 17th 2018: Good morning, As usual, Windows update slowed my computer down with an unannounced, unplanned update, on a Monday morning, interrupting productivity and eventually crashing the system, causing me to lose an estimated 2 hours of work despite saving at a recommended...
  10. Windows 10 V1809 update problem with Office 365 on Oct 02, 2018

    in Windows 10 Installation and Upgrade
    Windows 10 V1809 update problem with Office 365 on Oct 02, 2018: After performing the update at my desktop HP Workstation , whenever I started Outlook or any Office 2016 software there was a server connection problem reported. My IT Dept looked at it for a day with no resolution. They tried to un-install / reinstall Office - but it...

Users found this page by searching for:

  1. 405706ed-f1d7-47ea-91e1-eb8860039715