Application reconfiguration at every boot

Topic

New Reply

My Windows 10 Dell 8930 desktop computer started reconfiguring all applications every time I boot the computer. I am running version 2004, but the problem started well before this update. I’ve not been able to find any coverage of this issue and I don’t know how to stop it. I’m running Windows 10  version 2004 on a new Dell laptop and this situation has not occurred. I can’t find any topic like mine by searching the Lounge. Can you point me in the right direction? Thanks so much.

Tom Czechowski

Reply | Quote

Replies

This sounds like a WMI ‘consistency check’. These can have several causes and can be a pain to track down.

The most likely reason is installation of a new app. If, for example, the install writes to a temporary yet required file location which is subsequently deleted by automatic cleanup or – as another example – a filepath is changed, removed or corrupted (e.g. written to a damaged sector or as a result of registry corruption) then the MSI engine notices the missing location and decides to check ALL apps for integrity. Did you install a new app just before the issue started?

Have a look in Event Viewer for Event ID 1035 in Applications. Easier still, use Nir Sofer’s free, portable FullEventLogView and this will show ALL instances in a list rather than having to scroll through Event Viewer. Find the first recorded instance of event id 1035 then work backwards in the Application log (and sometimes the System log) until you find the app that was installed just prior (often followed by a restart) to the issue beginning. This is most likely the app that has an issue which is constantly being checked and triggering the rest of the consistency checks. Note, however, that this is not foolproof.

As it’s unlikely that a reason for the consistency check will be shown, re-install the app on top of itself. This will add the installation filepath info back into the registry. (If you are using a spinner HDD then carry out a CHKDSK /r on the drive before the reinstall so any damaged sectors are identified and marked ‘do not use’.)

Another possible reason is when the normal logged-on user account’s privileges changes. As an example, the first account created after OOBE (out-of-the-box experience) – i.e. the initial installation of Windows – is added to the Administrators group. If this account is subsequently changed to a standard account then it can trigger this issue because registry/file permissions have changed to lesser privileged. Have you made changes to the normal account used?

Yet another reason this can happen is when a Group Policy is applied (although this usually happens within a locked down environment, i.e. joined to a domain). Are you using Win 10 Pro on the desktop and made a change using the Local Group Policy Editor just prior to the issue beginning?

For backround info, have a read of the following Microsoft Support doc: Event log message indicates that the Windows Installer reconfigured all installed applications

Hope this helps…

Reply | Quote