DeviceSetupManager, Event ID: 121, 131, 163 and more ...

Some errors are: failed installation of a driver, Metadata staging failed or some sort of "software settings failed to install". I'm not clear on why, once the OS is loaded (without obvious errors), that DeviceSetupManager would be needed to install or load a driver or setting; post the OS booting successfully. These DeviceSetupManager errors come from out of the blue, after the box has been running (without issue) for awhile. Once started, their frequency increases.

Other DeviceSetupManager entries in 'Task Manager' --are pointing to Win-Update attempting to phone home. This machine has no immediate or near future plans --to connect to the Inet. Currently this machine runs more stable with the stock OEM drivers and the provided OS preload. Each and every time I let Win-Update touch this machine, the entire install goes sideways in short order.

I would prefer making the most of what I currently have, by fixing the current issues I find, starting with the above, until the dust settles with Win-Update. By 'fix', I mean stop the trigger that is generating these errors, without additional grief.

Follow the instructions for Option 3:
How to Turn On or Off Automatic Device Driver Installation in Windows 10

garlin said:

Follow the instructions for Option 3:
How to Turn On or Off Automatic Device Driver Installation in Windows 10

Click to expand...

To be clear, I'm using Win-11\Home.

That doesn't matter for this setting.

garlin said:

Follow the instructions for Option 3:
How to Turn On or Off Automatic Device Driver Installation in Windows 10

Click to expand...

I've just read the above link; thank you. Which leads to this, this is a fresh install by way of "keep personal files, delete all apps". The machine is not connected to the Inet. That said, what drivers and/or setting(s) is DeviceSetupManager trying to install?

DeviceSetupManager is trying to check if there's updated device icons or descriptions available for your current devices.

garlin said:

DeviceSetupManager is trying to check if there's updated device icons or descriptions available for your current devices.

Click to expand...

I think I'm beginning to understand, = because no Inet, everything is failing? I had initially thought it was trying to Install a driver residing locally on the machine. Finally, I thought this setting (link) was only after Win-Update was connected to the Inet. I would think the OS would be smart enough and check for a connection first. These log entries are truly numerous.

Thank you.

Query01 said:

DeviceSetupManager, Event ID: 121, 131, 163 and more ...
Some errors are:

Click to expand...

So what?
You have not mentioned any fault symptoms being experienced, merely events being logged in Event viewer.

The existence of an entry in an Event log is not really a sufficient indicator that there is a problem worth using your time & effort to investigate.
Conversely, if you are investigating a problem for which there are observable fault symptoms, Event logs can provide data that might be helpful.
I only look in Event logs if I'm investigating something.
If there's nothing to investigate then I don't look in them at all.

The Event logs exist for Windows' benefit not ours.
- For all us mere mortals know, particular events are logged in order for Windows to check for them & use them to trigger a repeat process which, if successful, does not get logged.
- Similarly, event log entries might be recorded merely as triggers for other Windows processes to refer to and successful completion of those other processes might well not be reflected in an Event log entry that can be recognised as being related to the first [trigger] entry.

Query01 said:

I would prefer making the most of what I currently have

Click to expand...

I agree. So just get on with using your computer.


All the best,
Denis

@Try3\Denis, unnecessary entries filing logs is a problem for me; as is storage space over time. If it weren't an issue --perhaps it should be logged at a lower level.