This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 48%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
DYMO Label Writer Duo Printer(Composite USB) does not work after updating windows 10 with KB5015807.
This is what we found.
Standard USB enumeration requests are identical between good vs bad hosts..
Basically, printer supports two interfaces, interface 0 (label) uses endpoint 2 while interface 1 (tape) uses endpoint 5.
Print class Get Device ID request, good host asks both interfaces correctly, interface 0 & interface 1…
Failed host asks interface 0 & 1 correctly (with correct max length), same a above good host..
But it asks interface 0 & 1 again (with wrong max length).. Though printer still replies with same IEEE strings (label & tape)..
And host seems only setup interface 0 (endpoint 2) correctly, but failed to setup interface 1 (endpoint 5) at all…
You might check on why host could not setup both interfaces as it did with good host with windows update..
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 54%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Thanks for your insights.
It's also not just the cumulative 2022-07 Update (KB5015807).
This bug is also present in 2022-10 (KB5018410)
I've also seen this bug using USB Device Tree Viewer, so it seems to be Windows at fault. (as the Label interface is all messed up and internally named "DYMO LabelWriter DUO Tape") This might also be a new security issue as wrong values are put at wrong places.
Which makes the work around quite bad as that would be to uninstall both and disable Windows Update all together...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 26%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Ok, just received yet another reply from Dymo Support, but incredibly they state:
Microsoft should be providing a permanent solution by the end of June/first week of July so I am happy to let you know your problem will be fixed soon.
YAH!
Safe and Effective == Highly Dangerous and Worse than Useless
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 79%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
Has the solution been delivered or do we still have to wait?
The problem is not solved for me yet.
Latest update for Windows 10 and 11 from Microsoft includes the fix for the issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Sounds like you may need to install this out of band update.
https://support.microsoft.com/en-us/topic/july-6-2021-kb5004945-os-builds-19041-1083-19042-1083-and-19043-1083-out-of-band-44b34928-0a71-4473-aa22-ecf3b83eed0e
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Do you suggest downgrade the update patch to previous version?
If that is what you suggested, Yes, Downgrade or remove the version of patch works fine with the printer.
This is not the correct solution for the issue.
The OOB is a later update.
--please don't forget to upvote and Accept as answer if the reply is helpful--
KB5015807 is the one with the issue, it is released on 7/12/2022.
https://support.microsoft.com/en-us/topic/july-12-2022-kb5015807-os-builds-19042-1826-19043-1826-and-19044-1826-8c8ea8fe-ec83-467d-86fb-a2f48a85eb41
KB5004945 is release on 7/16/2021.
Please, correct me if I misunderstand your point.
The OOB comes after KB5015807, so I'd install the OOB
--please don't forget to upvote and Accept as answer if the reply is helpful--
if the link is not correct, Could you share the link for download?
--please don't forget to upvote and Accept as answer if the reply is helpful--
I cannot find the link for the patch from the link. Can you just copy the download link only?
You can download directly here from catalog.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5004945
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thank you for your comments and help,
Windows 10 Enterprise.: version is 10.0.19044 Build 19044.
I cannot find the correct update for me, and I tried to install the version for 64 bit windows.
There is an error while installation.
Ok, that appears to be 21H2 where 5015807 is the latest cumulative update. You may need to wait to see if there will be an OOB released or alternately wait for the next monthly cumulative update.
https://support.microsoft.com/en-us/topic/windows-10-update-history-857b8ccb-71e4-49e5-b3f6-7073197d98fb
--please don't forget to upvote and Accept as answer if the reply is helpful--