Author Topic: Restart required after restart?  (Read 2938 times)

0 Members and 1 Guest are viewing this topic.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Restart required after restart?
« on: June 08, 2018, 11:46:11 AM »
Is this a known issue with Win 10 version 1803?
I got some updates yesterday, shut down last night, and rebooted this morning.

When I checked, "Updates" it indicated that I needed a restart for the "cumulative update".
When I check  "Update History" it indicates that the same update (and the others) were successfully installed.
The update troubleshooter found no problems.

see attachments:

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #1 on: June 08, 2018, 11:56:22 AM »
After I posted the above, I restarted again.
The symptoms are unchanged.
I'm concerned that if this persists, I won't be able to check for the next updates.

Offline Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 19100
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Restart required after restart?
« Reply #2 on: June 08, 2018, 12:22:52 PM »
Hi, Pete

I suggest starting with the Windows Update Troubleshooter.  If that doesn't solve the problem, I'd follow with SFC and, if no issues found, DISM:

  • Click on the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator
  • Enter the command(s) below and press on Enter
SFC:
Code: [Select]
sfc /scannow
DISM:
Code: [Select]
DISM /Online /Cleanup-Image /RestoreHealth


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #3 on: June 08, 2018, 01:54:14 PM »
Ran SFC /scannow .... It made some "fixes", but the symptoms remain.
Rebooted... No change
Ran the troubleshooter again... this time it fixed an issue with updates, but the symptoms remain.
While I'm typing this "DISM /Online /Cleanup-Image /RestoreHealth" is running in an administrator command prompt window.

The contents of the scannow log (CBS.log) follow:

2018-06-08 05:37:18, Info                  CBS    TI: --- Initializing Trusted Installer ---
2018-06-08 05:37:18, Info                  CBS    TI: Last boot time: 2018-06-08 05:33:22.494
2018-06-08 05:37:18, Info                  CBS    Starting TrustedInstaller initialization.
2018-06-08 05:37:18, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2018-06-08 05:37:18, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2018-06-08 05:37:18, Info                  CBS    Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2018-06-08 05:37:18, Info                  CBS    Ending TrustedInstaller initialization.
2018-06-08 05:37:18, Info                  CBS    Starting the TrustedInstaller main loop.
2018-06-08 05:37:18, Info                  CBS    TrustedInstaller service starts successfully.
2018-06-08 05:37:19, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2018-06-08 05:37:19, Info                  CBS    Startup processing thread terminated normally
2018-06-08 05:37:19, Info                  CBS    TI: Startup Processing completes, release startup processing lock.
2018-06-08 05:37:21, Info                  CBS    Starting TiWorker initialization.
2018-06-08 05:37:21, Info                  CBS    Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2018-06-08 05:37:21, Info                  CBS    Ending TiWorker initialization.
2018-06-08 05:37:21, Info                  CBS    Starting the TiWorker main loop.
2018-06-08 05:37:21, Info                  CBS    TiWorker starts successfully.
2018-06-08 05:37:21, Info                  CBS    Lock: New lock added: CCbsWorker, level: 5, total lock:3
2018-06-08 05:37:21, Info                  CBS    Universal Time is: 2018-06-08 09:37:21.638
2018-06-08 05:37:21, Info                  CBS    Loaded Servicing Stack v10.0.17134.1 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.1_none_eedfeda03074e04e\cbscore.dll
2018-06-08 05:37:21, Info                  CBS    Build: 17134.1.amd64fre.rs4_release.180410-1804
2018-06-08 05:37:21, Info                  CSI    00000001@2018/6/8:09:37:21.887 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffea1b6c2b9 @0x7ffea1ed2a06 @0x7ffea1eedf1f @0x7ff610ac2c32 @0x7ff610ac35e8 @0x7ffedeb84bf3)
2018-06-08 05:37:22, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
2018-06-08 05:37:22, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
2018-06-08 05:37:22, Info                  CBS    NonStart: Set pending store consistency check.
2018-06-08 05:37:22, Info                  CBS    Session: 30670485_229213330 initialized by client UpdateAgentLCU, external staging directory: (null), external registry directory: (null
2018-06-08 05:37:22, Info                  CBS    Session status queried: Current Phase: 1, Last SuccessfulState: Complete, Completed: 1, Status: 0x0
2018-06-08 05:39:23, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2018-06-08 05:39:23, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-06-08 05:39:23, Info                  CBS    Execution Engine Finalize
2018-06-08 05:39:23, Info                  CBS    Execution Engine Finalize
2018-06-08 05:39:23, Info                  CBS    Ending the TiWorker main loop.
2018-06-08 05:39:23, Info                  CBS    Starting TiWorker finalization.
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-06-08 05:39:23, Info                  CBS    CBS Engine already deativated
2018-06-08 05:39:23, Info                  CBS    CBS Engine already deativated
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: WcpUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: DrupUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: DpxUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: SrUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2018-06-08 05:39:23, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-06-08 05:39:23, Info                  CBS    Ending TiWorker finalization.

 

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #4 on: June 08, 2018, 02:14:49 PM »
"DISM /Online /Cleanup-Image /RestoreHealth" completed, symptoms unchanged.

Rebooted ..... FIXED  ;D ;D ;D
Checked for updates ... normal for when none are available...still fixed.

Thank You ! :)

Offline Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 19100
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Restart required after restart?
« Reply #5 on: June 08, 2018, 03:38:14 PM »
Glad that did it!


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #6 on: June 13, 2018, 06:05:42 PM »
It (sort of) happened again.

Yesterday, I checked for updates and got the cumulative update and the malicious software removal tool... After the download, the cumulative update was "pending restart".

When I shut down yesterday evening, it made me wait while updating. The boot this morning took some extra time to complete the process.

Later.... When I opened the "windows update" window it was still "pending restart"

This time the second restart worked.... BUT ? ? ?

BTW: The second restart didn't appear to be installing anything, and took no more time than any other routine restart.

Offline Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 19100
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Restart required after restart?
« Reply #7 on: June 13, 2018, 06:17:47 PM »
Someone in another forum reported the same thing.  My experience with KB4284835 yesterday was a bit different.

Yesterday afternoon neither Start nor Search would work on my Windows 10, version 1803 laptop.  However, right-click on the Windows key did work and I selected "restart and install updates".  After the restart, Start and Search worked again, Windows Update showed KB4284835 was installed BUT also showed that a restart was needed in order to install it.  I figured another restart wouldn't hurt but had the same results. 

The Windows Update Troubleshooter didn't find any issues so I ran DISM.exe /Online /Cleanup-image /Restorehealth while fixing dinner.  WU still showed a restart was needed but was busy with other things so decided to hold off restarting and, actually, forgot about the restart until this morning when I saw WU had done its thing and restarted overnight.  Low and behold, KB4284835 successfully installed and no more restart needed. 

Wondering if others were seeing the same thing, I located Windows 10 Cumulative Update KB4284835 Might Be Failing to Install as Well:

Quote
Microsoft says it’s aware of just one known issue in this cumulative update, but as it turns out, KB4284835 fails to install in some cases, eventually causing an infinite loop where the update is listed as successfully installed, only to be re-offered again after every boot.

There are several posts on reddit pointing to such an issue, and for the time being, no workaround appears to be available. Manually installing the update does not correct this behavior.

Whether it was the third restart (three's a charm), DISM or just plain luck, thought I'd share.

KB link:  June 12, 2018—KB4284835 (OS Build 17134.112)

 


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Offline DR M

  • LzD Friends
  • Hero Member
  • *****
  • Posts: 1494
  • Happy July 13th!
    • View Profile
Re: Restart required after restart?
« Reply #8 on: June 13, 2018, 06:36:40 PM »
I had the same issue with the restart. Something that might not have sense or relationship with the issue:
Computer 1: I chose Restart from the Updates page. The Restart need did not appear again.
Computer 2: I restarted as always (Start>Restart). The Updates page asked for a restart for the update to be completely installed.

I also received a message that the Updates have something to do with my organization policies. I didn't see that before. The message disappeared after I clicked on Check for updates button, so I don't have something to show you here.
Nothing...

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #9 on: June 13, 2018, 06:40:00 PM »
If MS is aware that there's a problem, I guess there's some hope that this isn't going to last forever.
BUT
When my friends at DunningFools act paranoid about Windows updates, I can no longer gloat about my 100% success record.

Offline pastywhitegurl

  • Hero Member
  • *****
  • Posts: 1010
  • advanced techno feeb
    • View Profile
Re: Restart required after restart?
« Reply #10 on: June 13, 2018, 06:41:23 PM »
It sounds like it might be a good idea to delay installing this update for a while.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #11 on: June 13, 2018, 07:49:17 PM »
It sounds like it might be a good idea to delay installing this update for a while.
I wouldn't go that far, (but some of my friends would).
It's not necessarily just this one update. This is the second one that acted strangely for me.

It might be a good time to update your disc image (if you maintain one), and make sure you have a new restore point prior to any updates.

Make sure you can find this topic again. So far when an extra reboot didn't work, the instructions that Corrine gave in her post of June 8 (above) got us out of trouble, even if it didn't prevent a recurrence.

~~~~~
Panos:
I get that group policies message too.
In my case I suspect it's unrelated to this problem, and possibly a side effect of my anti-telemetry software (ShutUp10) which overrides dozens of settings that I'd ordinarily have to set manually (if I could find them all).


Offline Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 19100
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Restart required after restart?
« Reply #12 on: June 13, 2018, 08:41:19 PM »
When my friends at DunningFools {SNIP}

Wow!  DF lives on!  I'm impressed.  I thought it shut down long ago.  I don't even recall if I used my standard username or something else there.  I didn't visit often but did stop in on occasion.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #13 on: June 14, 2018, 02:20:14 PM »
OFF TOPIC:
When my friends at DunningFools {SNIP}

Wow!  DF lives on!  I'm impressed.  I thought it shut down long ago.  I don't even recall if I used my standard username or something else there.  I didn't visit often but did stop in on occasion.
We went "under the radar" after the Netzero incident, and stayed there...
The original purpose is no longer relevant. It's now more like old friends/co-conspirators staying in touch. There are about a dozen everyday regulars, and a handful of others that check in now and then.

Your account used your usual screen name, but was purged long ago due to inactivity.

Offline Pete!

  • Hero Member
  • *****
  • Posts: 5156
    • View Profile
Re: Restart required after restart?
« Reply #14 on: June 27, 2018, 02:25:21 PM »
The second June update went smoothly.
Only one restart required.