Win upt-datll es causing blue screen, total shut-down.

Yes Noel IDP, yr correct ... SFC scan was not done properly. Trust this is a better result.
CBS files now uploaded and replaced earlier version in dropbox.

https://www.dropbox.com/sh/31idli9c1...7CkrAxgpa?dl=0

Despite the error messages in the SFC results you saw, there's nothing actually wrong (at least according to MS)

Code:

	Line 28160: 2015-07-21 09:24:57, Info                  CSI    0000037c [SR] Repairing 1 components
	Line 28161: 2015-07-21 09:24:57, Info                  CSI    0000037d [SR] Beginning Verify and Repair transaction
	Line 28164: 2015-07-21 09:24:57, Info                  CSI    0000037f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 28167: 2015-07-21 09:24:57, Info                  CSI    00000381 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 28170: 2015-07-21 09:24:57, Info                  CSI    00000383 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 28171: 2015-07-21 09:24:57, Info                  CSI    00000384 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
	Line 28174: 2015-07-21 09:24:57, Info                  CSI    00000386 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

These errors are the result of a coding error that MS hasn't got around to fixing yet (and don't hold your breath!) , and not a problem with anything on your system.
If you want to get rid of the 'error' message, you'll have to uninstall KB3068708 and hide it when it reappears in Windows Update.

There are no errors in the background of the latest CBS.log.

Try this...

Open an Elevated Command Prompt, and run the following command

RD C:\windows\SoftwareDistribution\Download\2055a44a789250d80968c99ba31bffb2 /s

respond 'Y' to any 'are you sure' messages, then reboot and do a Check for Updates.
see what happens then.

Ran the cmd (see screen shot) ...

At attempt to d/load Updates machine again entered blue screen and shut down.

Also attaching screen shot of the Update page which appears to be problematic.
Looked for KB3068708 in Updates previously installed but no sign of that number.

Not a totally unexpected result from the RD command.

That listing you posted is of the updates still waiting to be installed - you need to look at the Installed updates listing, and use the Search box for KB3068708

Ok ... I found KB3068708 and uninstalled it, then did a restart.

The the updates we know are those waiting to be d/loaded were retried.
The machine went into blue screen again and closed down.

You know Noel what gets me about all this is that I can't find a way to communicate with Microsoft ...even
phoning was a waste of time. You'd think they'd want to know wouldn't you, in case it's also affecting other
machines.

I appreciate yr imput but don't know what else I can do.... unless you have another suggestion?

Post Script:
went back to a mirror image...so lost a good bit of data... but discovered that this computer was signed on so have quickly 'Undone' Get win 10 .
https://answers.microsoft.com/en-us/...673b8af?auth=1

damn it ... I wouldn't mind betting that's the disturbance. Let's see if my blue screen stops.
I like this Win 7 Pro version, it's stable, I've set up and do not want to have to go through all that again with a new Win Version I don't want.

Ok, after hours online with Microsoft the problem has been located ... it was a corrupted driver in Microsoft Security Essentials (MSE). So my apologies for blaming the Win 10 offer (I'm aware it will knock out several programs including Win Media Center.

My computer is now up to date (Win Updates) and MSE has been uninstalled and a new vers. installed.
This thread is now complete.