How does DUMO work?

[GagliaudO16]

DUMO SOFTWARE:
Could it be possible to have a tutorial?
In what differs the PRO version in comparison to the FREE version?
Thanks a lot! Paolo

[Kyle_Katarn]

DUMO SOFTWARE:
Could it be possible to have a tutorial?
In what differs the PRO version in comparison to the FREE version?
Thanks a lot! Paolo

DUMo aims at being quite straight forward....

PRO version :
- removed "puchase now" reminder
- allow direct link to driver manufacturer site, skipping both DUMo page & Google search

Are you a registered user ?

[yarr]

All DUMo does is point you in the direction of where to get your drivers which is already pretty obvious if you know who made your drivers. It doesn't update or install the drivers for you unfortunately.

[Kyle_Katarn]

Will be improved soon !

[scheff]

I've another question on the feature set of DUMO. How can it be configured NOT to propose beta versions of drivers?

SUMO has a corresponding configuration option to suppress reporting of available beta software updates. But I didn't find such an option in DUMO. I prefer to have such an option in DUMO too, with not reporting beta versions as default.

On my notebook there are several drivers detected by DUMO carrying the same version number trunk as the operating system Windows 10. My device recently updated the operating system to version 1809 resp. 10.0.17763.437 while this kind of drivers is detected as being version 10.0.17763.1. For several of them, DUMO now reports available updates to version 10.0.18362.1. From an article [https://www.heise.de/ct/artikel/Windows ... 67985.html] on of a German computer magazine I learned that the current release candidate preview of Windows 1903 has build number 18362, that the release is expected by end of May 2019 with not yet known build number. The article was published on 12 April 2019. So these updates proposed by DUMO should be considered beta software.

I don't understand why there is a threat in the forum on beta versions and undue notifications by DUMO if I cannot configure DUMO to suppress reporting of beta versions. I'm running version 2.17.3.88 of DUMO.

[Kyle_Katarn]

Not possible yet, but good point => Added to the ToDo list : https://www.kcsoftwares.com/bugs/view.php?id=5439

[scheff]

All DUMo does is point you in the direction of where to get your drivers which is already pretty obvious if you know who made your drivers. It doesn't update or install the drivers for you unfortunately.

Driver updates by third parties like KC Softwares I consider sensitive and risky as I don't know which kind of information is taken into account and which one ignored. So while some users prefer either an automatic update or a 1-click action, I prefer to being asked between each step with the possibility to abort or revert. So if improvement goes into the simplification direction, I want to have corresponding option to prevent this simplification.

I still don't understand what is straight forward here. What you declare as straight forward or obvious is the abstract behaviour. But what about further details?

Depending on installed device, DUMo reports between 30 and 50 drivers while Windows reports several hundreds. What explains this large difference?

Even if I take a look at the log file, I see many detected drivers filtered out and never reported. Why?
And why this filtering doesn't get configurable?

I didn't store and analyze the log file. According to my impression even if this filtering would almost be suppressed after new configuration options provide such a choice, DUMo still remains far below the number of drivers detected by Windows device manager. The only filtering I understand is that if a particular device on the computer is installed several times, then the driver has the same number of instances and should be reported once as long as those instances don't have different versions of the driver installed.

As already reported, the beta version reporting option is missing in DUMo. I'm not interested in beta versions. And as already reported DUMo nevertheless reports versions to me as available regardless if they are released or still in beta state. DUMo can't know that I'm not interested in beta versions as long as this options doesn't get implemented.

I forgot to mention that the look at the log file reminded me that I've put some detected drivers on the ignore list due to this undue beta reporting. The size of the ignore list is well below 10 records. That doesn't mean that there are not beta versions reported available anymore but that the other beta versions I want to see although not install.

What's i.e. the DUMo design decision on installed drivers versus active drivers?

[Kyle_Katarn]

DUMo picks up all drivers being reported by Windows as installed and active.
Filtering some entries considered as meaningless, like SUMo does for some subproducts, dependancies, ...

[scheff]

DUMo picks up all drivers being reported by Windows as installed and active.

Do I understand right that drivers reported by Windows are detected, regardless if they're active or not?
And if they're not reported then because they're filtered due to being considered meaningless?

Filtering some entries considered as meaningless, like SUMo does for some subproducts, dependancies, ...

SUMo does report some subproduct and dependencies while filtering others. Its filtering can be further customized via ignore and remove lists. For DUMo, I only find this customization option of ignoring. I don't know if this is sufficient. I'm currently not interested to use a remove list neither for SUMo nor for DUMo.

With your explanation, I still don't understand some filtering. Why does DUMo consider the remote media server which is also Internet access point router as meaningful while considering another remote media server which is also a storage server as meaningless?

I've put (temporarily) various virtual drivers on my ignore list of DUMo. So I understand that they are filtered. Why are others (like Windows XPS driver and Windows PDF driver) considered meaningless and filtered out?

I don't know if cloud services and Microsoft Office services are integrated differently into Windows. But I see that OneNote and Send to OneNote are both filtered out and hence claimed to be meaningless. I may understand if Send to OneNote is considered meaningless if OneNote itself is reported. But why filtering out both?

And why are some network drivers filtered out while others are reported?
I understand some protocol specific drivers being filtered out like WAN Miniport (L2TP), WAN Miniport (IPv6), WLAN, Wi-Fi Direct Virtual Adapter, WAN Miniport (SSTP), WAN Miniport (IP), WAN Miniport (Network Monitor), WAN Miniport (IKEv2), WAN Miniport (PPTP) and WAN Miniport (PPPOE). I see the standard Windows virtual Fax driver filtered out while a PDF Fax virtual driver is filtered out only because I put it on ignore list. Why this difference?
And why are Hyper-V Virtual Switch Extension Adapter, Hype-V-Virtualizationinfrastructuredriver, and Hyper-V Virtual Ethernet Adapter all being considered meaningless and filtered out?

Windows has several tools for querying installed drivers. It looks like DUMo does only use the one reporting less drivers! Is my impression correct?

But why are sensor drivers like Accelerometer neither detected nor reported although it is active, nor AFD, afunix, ahcache?
It further looks like inactive or stopped drivers are neither detected nor reported by DUMo like AcpiPmi, AmdK8, AMDPPM, amdsata, amdsbs, amdxata, AppID, applockerfltr, APPvStrm, arcsas, AsyncMac, b06bdrv?
And why are BrCow, BrFilter neither detected nor reported although active?
Shall I continue that list of more than 420 drivers reported by Windows on this notebook?
(DUMo reports more than 40 and detects more than 50 only, the difference being on the ignore list.)

[scheff]

Or why are all drivers related by third party antivirus and security product and manufacturer neither detected nor reported?
Not even one is reported by DUMo as opposed to Windows!