Shutdown stopped working after the latest Windows10 automatic update

  1. dragonxi4tenfor's Avatar
    Posts : 37
    Windows 10
       #1

    Shutdown stopped working after the latest Windows10 automatic update


    Start > Power > Shutdown did not anymore shutdown the PC
    I had to do reset and restart Window 10 again

    What can be done ?

    command mode shutdown ?
      My Computer

  2. hTconeM9user's Avatar
    Posts : 2,806
    Windows 10 Home (x64) Version 2009 (build 19042.928)
       #2

    The way I do it is
    Right click start
    Then click Shut down or sign out
    Click the >mark then click Shutdown
      My Computer

  3. davidhk's Avatar
    Posts : 5,433
    windows 10 Pro ver 20H2 build 19042.867
       #3

    dragonxi4tenfor said:
    Start > Power > Shutdown did not anymore shutdown the PC
    I had to do reset and restart Window 10 again

    What can be done ?

    command mode shutdown ?
    I don't use the Shut Down option.
    I always use the Sleep option, and if I need to shut down I will right click at Start > Shut down or sign out > Shut down.

    I just used your method to shut down my Win 10 Home ( fully updated ) and it shut down fine.

    You said " Start > Power > Shutdown did not anymore shutdown the PC. "
    So what did it do after you hit Shutdown ? Nothing ? Was there an error message ?

    Please do a troubleshooting..................
    Run a system file check to look for corrupt files. It will try to do repair if any found.

    Right click at Start button > click Command Prompt (Admin) > at the flashing prompt, copy/paste this.......
    sfc /scannow

    > press Enter.
    It will take quite sometime.
    When finished, it will give you one of the 3 reports...............(paraphrasing)
    1. No integrity violation.
    2. Found corrupt files and repair successful.
    3. Found corrupt files but unable to repair.

    If the report is #1, your solution lies elsewhere.
    If the report is #2, check if your problems have been resolved.
    If the report is #3, use this method................
    In the same Command Prompt (Admin) windows, copy and paste this command...........

    dism /online /cleanup-image /restorehealth

    > press Enter.
    Again it will take some time.
    When finished, it will give you a report.
    Last edited by davidhk; 21 Jan 2016 at 09:24.
      My Computer


  4. Posts : 109
    Win 10 Pro 64-bit
       #4

    hTconeM9user said:
    The way I do it is
    Right click start
    Then click Shut down or sign out
    Click the >mark then click Shutdown
    That always works for me too. Never had a problem
      My Computer

  5. dragonxi4tenfor's Avatar
    Posts : 37
    Windows 10
    Thread Starter
       #5

    Deployment Image Servicing and Management tool failed


    Thanks for advice!


    Answer to questions:


    Unlike previous Windows 10 versions it did not shut down the PC
    i.e. it did not shutdown/stop hardware
    i.e. instead hardware was still running although - it only shut shut down screens
    no error messages, no nothing


    Actions based on advice:


    Step 1
    Right clicked at Start button > click Command Prompt (Admin)
    > sfc /scannow
    Found corrupt files but unable to repair. <-- Yes!


    Step 2
    Analyzed C:\Windows\Logs\CBS\CBS.log:


    Example of error types reported by by sfc:
    Lock: Error found, inverse lock order ...
    Error STATUS_TRANSACTIONAL_CONFLICT originated in function Windows ...
    Session: 30494579_3517093375 failed to perform Synchronous Cleanup operation ...


    Actions performed by sfc:
    Regeneration Candidates: 0
    Removal Candidates: 3
    Superseded/LDR (Delta Compression) Candidates: 734
    Null-Delta Compression Candidates:
    Mutable file Candidates: 30
    Boot-Recovery Candidates: 235
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 8


    Step 3:
    > dism /online /cleanup-image /restorehealth
    Deployment Image Servicing and Management tool Image Version 10.0.10586.0


    Error: 0x800f081f
    The source files could not be found
    use the "Source" option to specify the location of the files that are required
    to restore the feature <-- what feature ?
    see Configure a Windows Repair Source




    Step 4: analyzed C:\Windows\Logs\DISM\dism.log:


    Error types:
    [4336] [0x8007007b] FIOReadFileIntoBuffer1250): syntax error in filename, directory name or hard disk name
    [6200] [0xc142011c] UnmarshallImageHandleFromDirectory793)
    [6200] [0xc142011c] WIMGetMountedImageHandle3046)


    Warning types:
    Warning DISM DISM OS Provider: PID=4112 TID=2648 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder
    Warning DISM DISM Provider Store: PID=4112 TID=2648 Failed to Load the provider: C:\WINDOWS\TEMP\83FDD624-FE19-4EDC-9056-AB036E6A1869\PEProvider.dll
    Warning DISM DISM Driver Manager: PID=4112 TID=7152 Could not get boot critical status for the driver class {8ECC055D-047F-11D1-A537-0000F8753ED1} from driver store.


    End of run:
    2016-01-21 20:00:32, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2016-01-21 20:00:32, Info DISM DISM.EXE:
    2016-01-21 20:00:32, Info DISM DISM Provider Store: PID=3964 TID=6428 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-01-21 20:00:32, Info DISM DISM Provider Store: PID=3964 TID=6428 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-01-21 20:00:32, Info DISM DISM Provider Store: PID=3964 TID=6428 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    Step 5: viwed Configure a Windows Repair Source
    Updated: October 20, 2013 <-- old !
    Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2 <-- no Windows 10!


    Step 6: unresolved ? / tips needed !
      My Computer

  6. davidhk's Avatar
    Posts : 5,433
    windows 10 Pro ver 20H2 build 19042.867
       #6

    Your dism .......> restorehealth said " source files could not be found" because your ISO has the Install.esd.

    You need the Install.wim which can be obtained by downloading the ISO from Tech Bench.


    http://www.microsoft.com/en-us/softw...load/techbench


    Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.

    Then open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.

      My Computer

  7. dragonxi4tenfor's Avatar
    Posts : 37
    Windows 10
    Thread Starter
       #7

    Windows 10 Restore and Resource Protection succeeded with the download


    Thanks again!

    Actions taken based on your advice:

    downloaded the ..._x64.iso
    mounted it
    run DISM with appropriate parameters
    ...
    The restore operation completed successfully
    The operation completed successfully
    ...
    run the sfc /scannow
    ...
    Windows Modules Installer Worker started
    Windows Resouce Protection found corrupt files and successfully repaired them.
    Details included in windir\Logs\DISM\CBS.log
    ...
    analyzed windir\Logs\DISM\CBS.log
    ...
    The following actions performed:
    Regeneration Candidates: 0
    Removal Candidates: 3
    Superseded/LDR (Delta Compression) Candidates: 734
    Null-Delta Compression Candidates:
    Mutable file Candidates: 30
    Boot-Recovery Candidates: 235
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 8
    ...
    The following actions performed:
    Regeneration Candidates: 0
    Removal Candidates: 4
    Superseded/LDR (Delta Compression) Candidates: 734
    Null-Delta Compression Candidates:
    Mutable file Candidates: 28
    Boot-Recovery Candidates: 235
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 8
    ...
    Windows Resouce Protection ended as follows:

    CSI 00006269 [SR] Verify and Repair Transaction completed.
    All files and registry keys listed in this transaction have been successfully repaired
    CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    CBS TiWorker signaled for shutdown, going to exit.
    CBS CbsCoreFinalize: ExecutionEngineFinalize
    CBS Ending the TiWorker main loop.
    CBS Starting TiWorker finalization.
    CBS CbsCoreFinalize: ManifestCacheFinalize
    CBS CbsCoreFinalize: ExecutionEngineFinalize
    CBS CbsCoreFinalize: ComponentAnalyzerFinalize
    CBS CbsCoreFinalize: PackageTrackerFinalize
    CBS CbsCoreFinalize: CoreResourcesUnload
    CBS CbsCoreFinalize: SessionManagerFinalize
    CBS CbsCoreFinalize: CapabilityManagerFinalize
    CBS CbsCoreFinalize: PublicObjectMonitorFinalize
    CBS CbsCoreFinalize: Enter vCoreInitializeLock
    CBS CbsCoreFinalize: WcpUnload
    CBS Ending the TrustedInstaller main loop.
    CBS Starting TrustedInstaller finalization.
    CBS Ending TrustedInstaller finalization.
    CBS CbsCoreFinalize: DrupUnload
    CBS CbsCoreFinalize: CfgMgr32Unload
    CBS CbsCoreFinalize: DpxUnload
    CBS CbsCoreFinalize: SrUnload
    CBS CbsCoreFinalize: CbsEsdUnload
    CBS CbsCoreFinalize: CbsTraceInfoUninitialize
    CBS CbsCoreFinalize: CbsEventUnregister
    CBS CbsCoreFinalize: AppContainerUnload
    CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
    CBS Ending TiWorker finalization.

    VERY MANY THANKS FOR YOUR ADVICE from all our guys >> wwww.dragonxi.com
      My Computer

  8. davidhk's Avatar
    Posts : 5,433
    windows 10 Pro ver 20H2 build 19042.867
       #8

    Wonderful.
    You are welcome.
    Happy computing.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 07:20.
Find Us




Windows 10 Forums