Windows 10: Was There A Major Upgrade To Win 10 Today (12/13/15)

I had a message on my screen after I logged back in to my laptop today. It said "We've updated your computer". Then it switched to "All your files are right where you left them." and wouldn't do anything else for almost five minutes, but you could tell the PC was doing SOMETHING because I had the blue wait circle going and the screen was dimming and brightening rhythmically. After a couple of minutes, "Don't turn off your computer" appeared in smaller text underneath the "All your files are right where you left them" message. Then it switched to "We have some new features to get excited about." Then it booted to desktop.
I hadn't shut the PC down, it was just in screen saver overnight. It did this all on its own.
When I went into Windows Update to check my update history, it said I'd never updated Windows. (This is a Win 10 64-bit machine.)
Windows 10 notification center had a notice that updates had been installed, but I wasn't able to open it for additional details.
My wife's laptop did exactly the same thing.
It seems like it must've been a "stealth" update of Windows 10.
Both laptops did this all on their own while unattended. This smacks of Microsoft being their pushy selves again.

Does anyone know what is going on with this?

:)

 

Windows 10 Upgrade Error 0x80004005 with unrepaired files after sfc/scannow

Here is the log summary, not sure how to repair these:

2016-12-15 10:33:12, Info CSI 000058fa [SR] Verify complete

2016-12-15 10:33:12, Info CSI 000058fb [SR] Repairing 1 components

2016-12-15 10:33:12, Info CSI 000058fc [SR] Beginning Verify and Repair transaction

2016-12-15 10:33:12, Info CSI 000058fd Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll"
:

Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2016-12-15 10:33:12, Info CSI 000058fe [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
in the store, hash mismatch

2016-12-15 10:33:12, Info CSI 000058ff@2016/12/15:15:33:12.707 Primitive installers committed for repair

2016-12-15 10:33:12, Info CSI 00005900 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll"
:

Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2016-12-15 10:33:12, Info CSI 00005901 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
in the store, hash mismatch

2016-12-15 10:33:12, Info CSI 00005902 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"

2016-12-15 10:33:12, Info CSI 00005903 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :

Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2016-12-15 10:33:12, Info CSI 00005904 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll"
:

Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2016-12-15 10:33:12, Info CSI 00005905 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

2016-12-15 10:33:12, Info CSI 00005906@2016/12/15:15:33:12.742 Primitive installers committed for repair

2016-12-15 10:33:12, Info CSI 00005907 [SR] Repair complete

2016-12-15 10:33:12, Info CSI 00005908 [SR] Committing transaction

2016-12-15 10:33:12, Info CSI 00005909 Creating NT transaction (seq 2), objectname [6]"(null)"

2016-12-15 10:33:12, Info CSI 0000590a Created NT transaction (seq 2) result 0x00000000, handle @0x1264

2016-12-15 10:33:12, Info CSI 0000590b@2016/12/15:15:33:12.767 Beginning NT transaction commit...

2016-12-15 10:33:12, Info CSI 0000590c@2016/12/15:15:33:12.779 CSI perf trace:

CSIPERF:TXCOMMIT;12954

2016-12-15 10:33:12, Info CSI 0000590d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

2016-12-15 10:35:13, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

2016-12-15 10:35:13, Info CBS TiWorker signaled for shutdown, going to exit.

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

2016-12-15 10:35:13, Info CBS Ending the TiWorker main loop.

2016-12-15 10:35:13, Info CBS Starting TiWorker finalization.

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: ManifestCacheFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: PackageTrackerFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CoreResourcesUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: SessionManagerFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CapabilityManagerFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: WcpUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: DrupUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CfgMgr32Unload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: DpxUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: SrUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CbsEsdUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: CbsEventUnregister

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: AppContainerUnload

2016-12-15 10:35:13, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.

2016-12-15 10:35:13, Info CBS Ending TiWorker finalization.

2016-12-15 10:35:13, Info CBS Ending the TrustedInstaller main loop.

2016-12-15 10:35:13, Info CBS Starting TrustedInstaller finalization.

2016-12-15 10:35:13, Info CBS Ending TrustedInstaller finalization.

 

win 10 uninstall does not work

Win 10 installed 11/22/15. Today is 12/9/15. Less than 30 days. When I go through the steps to uninstall, all the computer does is reboot. C:\WIndows.old is still there.

 

From what you describe it sounds like the November update to W10 TH2 Ver. 10586, you can right click on start, click run, type winver, click ok or press enter. This will tell you what version of windows your computer has installed.

edit: Not necessarily a "stealth" update, new versions of W10 will come through windows update like any other updates

 

current version 1511 build 10586.29

 

This is why auto-updates is a bad idea

 

Its better to be updated then not to be. but there have been some updates that could cause trouble. I did not see any update today and the current version of windows 10 is 10586.29.

 

You can check your latest Installed update via: control panel-> program and features-> view installed update.
(In case if you didn't know wheres is control panel, win10 seems to hide control panel into nowhere, you can find by going to: right click into windows logo at taskbar -> search, in column search, type control panel. or fastest way Windows+R - > control panel > enter)

Mine said it does update KB3116900 and several update to the office 2013. 12/13/2015

KB3116900 does change your windows version to newer version, as far as i search the information.

You can check your windows version via: type Windows+R-> type cmd then enter -> type winver, enter

My Windows also does automatically install this update when my PC was idle.
Btw i Got a several bugs after installation completed = >After Upgrade to the latest 10010586, HDD appears in Safely remove HW - Windows 10 Forums

 

10586.29, 1511 - Thank you all for the replies. The right-click on the new start button was a good tip, I'd not tried that before, strangely enough.

I WAS in Windows Update yesterday and looked at the update history, it showed as if there had never been any updates done - and I know for a fact that this machine had installed a few updates since it was upgraded to Windows 10.

Whoever wrote this update for Microsoft was a fool. This is exactly the kind of poor programming that generates backlash.

• No warning.
• No explanation to the user that it even was a Microsoft/Windows update.
• No explanation that it would wipe the Windows Update history out to zero.
• A note about "Your files are right where you left them" that makes it sound like potential ransomware.

Communication is the key to a good customer experience. Microsoft has clearly forgotten that fact.

 

I agree with your last two sentences. We are overdue with some info on networking problems as well.

 

I feel like it's been properly communicated, to be honest. I have two laptops running Home and a tower running Pro. I am well aware that the Home versions will update on their own.

 

Same thing happened to me yesterday on my flex 3. Upon reboot after the update it flashed an error message about a power driver error and my wifi is connected but says no internet access. Still can't figure out how to fix it.

 

Try running CMD (Command Prompt) and see if you can ping Google.com - if you can, it sounds like firewall, browser settings, or a similar setting right there on the device.