NY wrote:
"Paul" wrote in message
news
NY wrote:
Has anyone experienced and fixed this bug. It seems to be fairly
common according to the number of google matches. The absence (or
corruption) of \windows\system32\logonui.exe seems to be implicated,
with a lot of fixes being ways of copying the file from a saved
version (if one exists) or else copying from another PC. But is that
the whole story?
You can apply both "dism" and "sfc scannow" to an offline C: partition.

Normally, you'd use DISM like this (while the OS is running).

Dism /Online /Cleanup-Image /ScanHealth

sfc /scannow /offbootdir=C:\ /offwindir=D:\Windows


Preliminary report: I've got the PC working!

I found that c:\windows\system32\logonUI.exe was missing so I copied on
the one from my Windows10 PC and it booted perfectly. Goodness knows how
the file came to have disappeared: it wasn't as simple as it being in
the Recycle Bin (though I'd expect it to be locked so it can't be deleted).

The big question is: what else has disappeared at the same time. I'm
running "sfc /scannow" - at the moment at it's about 15% through the
verification phase at present. I might try the DISM commands as well to
be sure.

Thanks to everyone for their help - and thanks to the various forums
which referred to restoring the missing/corrupt file. I never thought it
would be so simple.

That should not happen.

Maybe an aborted Windows Update (kill power in the middle of
an update) could do it. Otherwise, not.

Files in the System folder, are protected by system file protection.
If you remove a file, the system should put it back.
(At least, as long as *some* copy of the file is present
on C: ).

The necessary copy is sitting in WinSXS. (For stuff like drivers,
there's a separate cache folder for those.) Files from WinSXS
are "hard-linked" into the System folder.

A combination of offline DISM and offline SFC should have
been able to fix that (DISM downloads the file, SFC makes
sure it's hard linked in and so on). And not break any
hard linking methodology in the process.

My guess is, your AV got a "false positive" on the file,
and quarantined it. Check the quarantine directory (if
you can find it). That seems a less coincidental explanation
than the file just "disappearing" on its own. AV programs
make mistakes occasionally, and for some, the damage
will be done, before the AV vendor can push out
a retraction.

Something happened to my "Inventory Agent" invagent.exe
or so, on my Win10, and that's where I got my chance
to practice with the offline DISM and SFC.

Paul