Brother QL-710W P-touch Address Book and Editor 5.2 disappear missing after update -- Error 1321 api-ms-win-core-file-l1-2-0.dll
Published: Thursday, February 28, 2019 written by Drew Jackson
so, you are using windows 10 and your QL-710W label printer stops working and the software update tool wipes out your software, label editor, and driver, and address book. Good thing is that I once got the driver reinstalled, even when troubleshooting thinking it was the QL-710W firmware update, nope, the usb driver, nope, USB2 vs USB3 port, nope..oh. btw, I fully disabled the Windows 10 Defender (MSE) antivirus too. tried that. nada.. nope..
then just to get the windows 10 64 bit drivers to install.. manually, override, to a USB 2 port, add manually, have disk, specify folder of extracted files... whew!! once driver back in there.. now the applications kept faulting.. here is why... PS. my address book full of entries were still there even after all of this... v1.3 of address book worked .. whew.. the rest is more or less a major pain.. even tried the power clean from brother for this little label printer.. and rebooted.. nada.. so as 10am today.. and then started back at 7pm tonight... got it fixed..
So, after 3 hours of testing, thinking its the driver, etc. Its really a permissions issue in three locals; c:\windows\temp, and %appdata%\temp and your windows SysWoW64 directory of DLL files that need to get updated from 2015 to 2016 versions but the temp installer of an MSI fails and shows in the Event Viewer | Application log files as such:
Brother P-touch Editor 5.2 -- Error 1321. The Installer has insufficient privileges to modify the file C:\WINDOWS\SysWOW64\api-ms-win-core-file-l1-2-0.dll
once the setup begins, once prompted to click install ok, go get the MSI file from the temporary installation folder... something like pftE0F6.tmp in the users appdata local temp folder.. something like pftE0F6.tmp\Editor52\ADE...
Directory of C:\Users\username\AppData\Local\Temp
10/10/2017 11:34 PM 32,489,984 AdBook13.msi
08/07/2018 01:57 PM 26,548,224 Ptedit52.msi
from the cmd prompt w/admin mode/privs, you can launch each of the MSI above and you will get the error message on screen rather than just ignored and not shown.. your Application log file will show the error but just once on the first DLL and stop and back out the install and say completed but really failed. note: the elevation of the setup EXE program to the carry through to the MSI. why? why not? who knows.
so, the permissions, need to add Everyone with Full permissions on c:\windows\temp, and on your C:\Users\username\AppData\Local\Temp folder, and launch the MSI's from the administrative command prompt, and change the permissions when prompted for the following group of DLLs.
note: not all of them, but the ones when prompted.. just Edit the Security Permissions on the DLL being argued with and click Users and check all the permissions and ok, and then click Retry.. it takes like 15 DLL error messages but it finally works.. see my notes below the screen shot..
its a royal pain in the ass. not sure what problems that windows 10 and brother has, but it could be a conspiracy.just add full permissions to each DLL when error pops up for the Users entry. Note most of the 2015 DLLs get updated to 2016, for good or bad. Could be my VS 2017 Development packages causing the problems but who knows.
more to come...
if you found this article helpful, consider contributing $10, 20 or so..to the author. more authors coming soon
FYI we use paypal or patreon, patreon has 3x the transaction fees, so we don't, not yet.
© 2019 myBlog™ v1.1 All rights reserved. We count views as reads, so let's not over think it.