Microsoft security update failed

When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

On 14/02/2018 14:33, Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Please download it manually from this page:

https://www.microsoft.com/net/download/windows

https://i.imgur.com/bfocvDT.png https://i.imgur.com/bfocvDT.png

--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 2/14/2018 6:33 AM, Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg


I generally try the update one or two more times (never more than two
more). If they still fail, I hide the update

--
David E. Ross
http://www.rossde.com/

President Trump: Please stop using Twitter. We need
to hear your voice and see you talking. We need to know
when your message is really your own and not your attorney's.

Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Do you actually use .NET 4.7.x for anything?

Paul in Houston TX wrote:
Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Do you actually use .NET 4.7.x for anything?


Yeah, that's what bothered me about this thread.

But how to write a reply that raises the issue diplomatically.

It's not really a security update.

The top of the diagram here, looks like that .NET package
is "part of the Microsoft business plan" and is not
really end-user focused. It has the words UWP in it
(or whatever the new buzzword and crazy scheme is
this week).

https://en.wikipedia.org/wiki/.net_framework

There's a taste of the brave new world here.
I wonder if it will be that flat and ugly
when run in Windows 7 ? Does Windows 7 have a Store
icon yet ? How will that program get delivered to you ?

https://docs.microsoft.com/en-us/win...xaml-universal

Paul

On 15/02/2018 05:22, Paul in Houston TX wrote:
Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Do you actually use .NET 4.7.x for anything?


Some modern .Net Apps will require it. Windows 10 is bundled at OS
level while Win7 and 8.1 will need to download them manually if not
offered automatically. Apps will bundle run-time libraries but some may
not create a standard installer files for their Apps.



--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On Thu, 15 Feb 2018 03:05:54 -0500, wrote:

When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Do you actually use .NET 4.7.x for anything?


Yeah, that's what bothered me about this thread

Some of the picture editors (Pinta? Paint.NET?) must have added .NET crap.

On Wed, 14 Feb 2018 20:35:38 -0800, wrote:

I generally try the update one or two more times (never more than two
more). If they still fail, I hide the update

I didn't realize a failure was a temporary thing.

Jose Rodriguez wrote:
On Thu, 15 Feb 2018 03:05:54 -0500, wrote:

When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg

Do you actually use .NET 4.7.x for anything?


Yeah, that's what bothered me about this thread

Some of the picture editors (Pinta? Paint.NET?) must have added .NET crap.

You can download the offline or web installer for 4.7 from Windows:
https://www.microsoft.com/en-us/down....aspx?id=56116
https://www.microsoft.com/en-us/down....aspx?id=55170
Maybe the updates will work after a reinstall of 4.7.

I have two programs that require .NET 4.5. One for pipeline laminar flow vs.
turbulent flow calculations and one for creation of a temporary server to be
used for remote programming of SCADA equipment. Other than those two I do not
use or allow programs that use .NET on my computers. I never update .NET unless
the two programs require a new version of .NET.

On Sat, 17 Feb 2018 10:54:30 -0600, Paul in Houston TX
wrote:

I have two programs that require .NET 4.5.


A clarification on the terminology: The programs don't require .net
4.5. They require the .net 4.5 *Framework*. They were written with
..net.

Ken Blake wrote:
On Sat, 17 Feb 2018 10:54:30 -0600, Paul in Houston TX
wrote:

I have two programs that require .NET 4.5.


A clarification on the terminology: The programs don't require .net
4.5. They require the .net 4.5 *Framework*. They were written with
.net.

More specifically, they'd be missing the CLR runtime support.

A regular program, for standard libraries in Win32, might
have used msvcrt.dll as a system DLL. Cygwin (some Linux
ports) uses a couple DLLs that provide their flavor of
runtime (cyggcc_s-1.dll and cygwin1.dll). The programs
will not run, without the basic support file, whatever scheme
is boiled into the program loading design they decide to use.
Anyone who has used Windows for a while, will have run into
the "missing Visual Studio" runtime, for which there is a
"Redist" available for download to fix it. Some things never
change.

A .NET program has a CLR boiled into it, seeking
runtime support for it. You might see an "mscoree" error
if the dependency is not met, implying mscoree has
something to do with loading the necessary DLLs.
These are some CLR versions (info that was removed from Wikipedia
by some monkey, so I can't give a Wiki reference).

..NET CLR 2.0.50727
..NET CLR 3.0.30729
..NET CLR 3.5.30729
..NET CLR 4.0.30319

*******

If you have an EXE and you want to know what CLR it is looking
for, there are a couple utilities.

The utility here, is a mechanical checker. It inspects certain
hex offsets in an EXE, and finds the CLR version there.

https://www.jsware.net/jsware/scrfiles.php5#peops

peops.zip == Check1FileForDotNet.vbs

I tested PaintDotNet.exe on that and it returned 4.0.30319.

https://s14.postimg.org/uk1vtgbvl/Ch...or_Dot_Net.gif

The download ZIP also has a file explaining why and how it's
designed the way it is.

*******

The second kind of checker, seems to attempt to load the assembly,
then ask for metadata. But, as the ReadMe for the previous software
mentions, this approach requires .NET to fish for the .NET version.
A highly undesirable result. And I ran into a problem with this
right away. The executable won't work properly, as currently delivered.
The executable needs to be recompiled to "stay up to date" itself.

"Simple utility to tell you the CLR version that an assembly wants. Source code included. 29.25 kb - 10/4/2010"

https://web.archive.org/web/20120718...les/clrver.zip

The program code is dead simple.

class Program {
[PermissionSet(SecurityAction.Demand, Name = "FullTrust")]
static void Main(string[] args) {
try {
string _fn = args[0];
_fn = _fn.Normalize();
if (args.Length 1) {
Console.WriteLine("0");
return;
}
Console.Write(_fn);
Console.Write("=");
if (!(System.IO.File.Exists(_fn))) {
Console.WriteLine("-1");
return;
}
Assembly a = Assembly.LoadFrom(_fn);
Console.WriteLine(a.ImageRuntimeVersion); === metadata...
} catch (System.BadImageFormatException ex) {
Console.WriteLine("NotCLR");
} catch (Exception ex) {
Console.WriteLine("-2");
}
//Console.WriteLine("hit any key to continue");
//Console.ReadLine();
}
}

The download contains a binary

CLRVer\bin\Release\CLRVer.exe

but it's compiled against .NET 2.0 and won't work with later
executables. I had to pull it into Visual Studio 2015, load
the .csproj, get it to change the manifest to a later version
of .net, then select the Build option from the menu to make
a new executable.

https://s14.postimg.org/vz3gihpwx/de...tput_Win10.gif

And it still says 4.0.30319 .

However, if I open the Paint.NET .config containing the assembly information...

?xml version="1.0"?
configuration
runtime
gcAllowVeryLargeObjects enabled="true"/
generatePublisherEvidence enabled="false"/
legacyCorruptedStateExceptionsPolicy enabled="true"/
loadFromRemoteSources enabled="true"/
/runtime
startup useLegacyV2RuntimeActivationPolicy="true"
supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/ ===
/startup
appSettings
add key="EnableWindowsFormsHighDpiAutoResizing" value="true"/
/appSettings
/configuration

it defines two fields. And I don't know what the "sku" field
means, in terms of preventing a user from using the program.
Does it gate the installation of the program ? Does it
gate the runtime ? Dunno.

Anyway, that's some fun with checking from the user end
of things, what it might need.

Maybe if I did a repair install, I could take that OS back to
4.0.30919, and then see if Paint.NET complains. But the Paint.NET installer
is also armed with a 4.7.1 stub, and I suspect given half
a chance, the wacky thing will fix conditions for itself
and ruin my experiment. A more poorly written program is needed,
one that isn't quite as "self-healing".

Because these questions don't come up all that often, I have
to assume .NET is "almost dead". As only parts of the OS
are written in it, to annoy (when there is an NGEN issue).

Paul

On 2/14/2018 6:33 AM, Jose Rodriguez wrote:
When a Microsoft "recommended" security update "failed", what are we
supposed to do about it?

http://i.cubeupload.com/jHKVNr.jpg


Which .NET update failed for you? That is, what is the KB number?

--
David E. Ross
http://www.rossde.com/

President Trump: Please stop using Twitter. We need
to hear your voice and see you talking. We need to know
when your message is really your own and not your attorney's.