Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

Hey guys,..

Two of my machines received version 1703-build-15063.138, However, the other laptop (which I did not get the

early release of the creators update on ) , stayed at ver-1607 build -14393.1066, The previous build was14393.970

I was kind of expecting the 1607 version to update to the 1703 version.Will this come in time ?

Forgive my inexperience, but is this Ok ? Thanks !

swarfega said:

They're staggering the release of Creator's Update so it might be a while until you get yours.

OK Thanks !! I guess I was just getting ahead of myself. Appreciate the response !

clam1952 said:

Same here 30 infected files but no malicious files found, bizarre eh?

Yea, a couple others have reported things awry with MRT also. Bizarre it is.

wordsworth said:

Yea, a couple others have reported things awry with MRT also. Bizarre it is.

I also wanted to report the same problem is occurring on windows version 1607 (os build14393. 1066 ) . Started after the update today

Ray14120 said:

I also wanted to report the same problem is occurring on windows version 1607 (os build14393. 1066 ) . Started after the update today

So the MSRT is broken for 1703, 1607 and 1511 then. Anyone running 10240?

Oh, wait... I am (or at least, I have a system image for it on my test machine). If it's broken there too, that completes the set :)

Cliff S said:

To see if MRT ran and the results open up the RUN dialog and paste this in: %WINDIR%\debug\mrt.log

Mine looks like yours, it apparently ran successfully.

Code:

---------------------------------------------------------------------------------------
Microsoft Windows Malicious Software Removal Tool v5.47, April 2017 (build 5.47.13703.0)
Started On Tue Apr 11 18:09:07 2017
Engine: 1.1.13601.0
Signatures: 1.239.313.0
Run Mode: Scan Run From Windows Update
Results Summary:
----------------
No infection found.
Successfully Submitted Heartbeat Report
Microsoft Windows Malicious Software Removal Tool Finished On Tue Apr 11 18:11:20 2017

Return code: 0 (0x0)

So why does the Reliability History report that it crashed?

Source
Microsoft Windows Malicious Software Removal Tool

Summary
Stopped working

Date
11/04/2017 18:11

Status
Report sent

Description
Faulting Application Path: C:\Windows\System32\MRT.exe


Problem signature
Problem Event Name: APPCRASH
Application Name: MRT.exe
Application Version: 5.47.13703.0
Application Timestamp: 58dec9f9
Fault Module Name: combase.dll
Fault Module Version: 10.0.15063.0
ault Module Timestamp: 3a54a041
Exception Code: c0000005
Exception Offset: 00000000000beab8
OS Version: 10.0.15063.2.0.0.768.101
Locale ID: 2057
Additional Information 1: eabd
Additional Information 2: eabd5fbe19958e4bb807d730fafe8b55
Additional Information 3: 911e
Additional Information 4: 911e7b429e9a5c27f92193dc4f77299


Extra information about the problem
Bucket ID: f166378dcb696f76ffdea3c4a5341044 (120736444423)