[1803, au] July Windows update - borked explorer.exe

[timbo343]

It would seem my machine that i use at work has decided to update to 1803 and now when any users, even local admin log in, all i get is the black screen. The only way i found to get round this is to run explorer.exe from task manager, then the GUI shows.

 

I thought these days has been and gone... obviously not.

 

Now recovering to 1709 - for gods sake MS!

 

UPDATE: Rolling back to 1709 has fixed the issue.

Edited July 11, 2018 by timbo343

[supportman]

Another reason to stay on LTSB! I've found so many problems with 1803 already, it seems Microsoft are still changing internal workings of the operating system at pace.

[free780]

Impero isntalled by any chance or a lot of firewall rules on your PC?

[Arthur]

Now recovering to 1709 - for gods sake MS!

You may find it useful to run SetupDiag to determine the cause.

 

Like @free780 said, it might not even be Microsoft's fault.

[timbo343]

I do have impero installed on the machine and i did think that once i saw the issue.

 

I will be removing impero from the machine tomorrow as im out this afternoon and seeing what the update does.

 

We only have education on our machines in the IT office and the rest of the network is LTSB for the reasons above.. for thr last 2 years its been solid and any issues have been quickly ironed out.

[timbo343]

So, removing Impero kinda ensured 1803 was successful. I managed to login to the machine with a user straight after the upgrade and explorer.exe didn't need to be run via task manager however when i tried with a different user (local admin) the OS failed to load explorer.exe so i had to run explorer.exe from task manager to get the GUI to load.

 

Now reverted back to 1709, ran SetupDiag and it didn't really give me anything. It ran and it closed. I was hoping it would have shown errors but this wasn't to be.

 

Looks like i will be sticking with 1709 for a bit longer.

 

EDIT:

 

Here are the results:

 

 

Matching Profile found: FindFatalPluginFailure - E48E3F1C-26F6-4AFB-859B-BF637DA49636

System Information:

Machine Name = {NETBIOS NAME}

Manufacturer = Hewlett-Packard

Model = HP Compaq 8200 Elite SFF PC

HostOSArchitecture = x64

FirmwareType = PCAT

BiosReleaseDate = 20111110000000.000000+000

BiosVendor = Default System BIOS

BiosVersion = J01 v02.15

HostOSVersion = 10.0.16299

HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908

TargetOSBuildString = 10.0.17134.1 (rs4_release.180410-1804)

HostOSLanguageId = 1033

HostOSEdition = Professional

RegisteredAV =

FilterDrivers =

UpgradeStartTime = 11/07/2018 11:07:35

UpgradeEndTime = 12/07/2018 09:20:21

UpgradeElapsedTime = 22:12:46

ReportId = 872b5fd3-55ef-440d-8999-daf4b8bbcdf8

 

Error: SetupDiag reports fatal migration plug-in failure. Plug-in Name = %windir%\system32\IasMigPlugin.dll, Migration Operation = IPostApply->PostApply, Plug-in Error: 0x00000032

Refer to https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-error-codes for error information.

Edited July 12, 2018 by timbo343

[TwistedHelixis]

Would this be the quick access issue I had with the latest build that would crash explorer????

 

My fix was

right click on quick access (if you can open explorer)- options and untick files. - I also anticked folders and changed open this computer to This PC, but dont think these last two are needed to fix the issue.

Edited July 12, 2018 by TwistedHelixis

[timbo343]

Im not sure if that will solve the issue. I'm tried to find what IASMigPLUGIN.DLL is and no where online says what i actually does apart from been linked to NPS. There are a few others on other forums that are having an issue with IASMIGPLUGIN.DLL but no solution has been found yet.

[Mic_Impero]

Hi all,

 

Sorry I'm late, I've been out visiting a great bunch of customers.

 

Just to clarify what we've seen at our end, there are some instances of Impero causing this, and the dll injections in place from version 6 onwards (which @timbo343 you already have from the original issue) resolve this. We've seen some other conflicts which entering dllhost.dll resolves, and this is in the software by default as of version 7.1. This will be due during August. In the mean time if anyone needs a hand with how to add this injection exclusion, please PM me.

 

For anyone running Kaspersky 11, we've discovered just today that version 10 doesn't inject dwp.exe and version 11 does, which we inject at the same time, and this can cause this issue also. Excluding dwp.exe from Impero injections will resolve that. I haven't heard of 1803 being involved specifically though, we've only seen this in an environment where Impero is already in place and a customer updates from Kaspersky 10 to 11, or installs Kaspersky 11 from scratch.

 

The vast majority of Impero HQ is running 1803 (and Sophos) and the Impero client and we've not seen any issues like this at all. Some have been from updates and some have been fresh builds, across a mix of bespoke computers and Dell optiplex kit, lenovo, dell, and asus laptops. We also carry out extensive testing of various Windows 10 builds including 1803 and haven't seen this issue.

 

I'll ask dev and our own infrastrucutre manager whether there's any no Impero related ideas they can think of to help identify the cause when i'm back in the office on Monday.

 

Hth

Mic

[timbo343]

Hi Mic

 

Do we know when 7.1 will be out in August? Any reason why you're missing out on 7?

[Mic_Impero]

Hi Timbo,

 

We're not missing out on 7, it's in early adopter now and going to full release tomorrow.

We're about to move to a monthly release cycle and so 7 will be tomorrow, and 7.1 will be as near as possible to a month afterwards.

 

What that does mean is you may see that we're on version 7, but your fix isn't coming until 7.2, for example, and that will be because 7.1 is code complete and in testing. But what it also means is you're only 2 months max from 7.2 instead of a term away max. This means we'll be able to develop faster, with less risk to each release, and you'll get any fixes and new features faster too. It isn't necessary to upgrade every time (although we'd encourage it) so if you don't benefit from anything in the 'next' release and you'd rather wait until the school holidays for example, and keep to doing it only a few times per year, you can still do so.

 

Mic

[timbo343]

Sooo... in terms of any upgrades over the summer, will be likely to see version 7 over the summer so we can at least get things up to date now ready for machines to be re-imaged over summer?

[Mic_Impero]

You're likely to see version 7 today, and 7.1 on the 18th of August all being well.

 

If you'd like to plan to do this only once and go straight to 7.1 towards the end of August, that would be understandable. In scenarios like this a monthly release doesn't benefit schools who aren't using the software for these weeks, but for the majority of the year it's a benefit (and in today's global market, summer holidays are at different times).

 

If you're building a new image, put 7 on your new image now, and you have the option to then roll them up to 7.1 at your convenience, and if you're not going to benefit from a fix or feature in 7.1 you can leave them on 7, and go straight to a later release later in the year, for example.

 

Thanks

Mic

[timbo343]

Cheers Mic.

 

What's new in 7, 7.1 and 7.2? I've not seen any release notes. Are you able to email me them or post them on here?

[free780]

Is it called Impero as a Service?

[Mic_Impero]

Hi Tim,

 

Release notes for the product are sent at the same time as the product release; as soon as it's the latest version it also appears in the server application.

I can make a habit of pinning them to the top of the direct support forum too as another place to find them easily.

@free780 There's nothing here named Impero as a Service. Most things as a service are SaaS based products hosted in the cloud. You can purchase Impero on a SaaS license which is less money up front, but less economical long term.

 

Mic