I was able to install using files from another x64 PC. I ended up creating a 7z file of the files in the %temp% folder indicated above. I then copied the file to the PC having issues and unzipped into a new folder. On right mouse click on the DYMO Label.msi and selected "Install". It worked without a problem. I have the 7z file which is large (240MB) and would upload it but not sure how. (This is my first 'reply' but I struggled with this issue for about a month and finally found this thread and was able to successfully install the program.) If you want me to send the file to you reply to this post and provide an email address and I will send it to you. This is an image of some of the files.
Windows ® Installer. V 5.0.19041.1 ?
Trying to install the driver for a dymo labelwriter 4XL and the message is what comes up. Any help is appreciated
Windows ® Installer. V 5.0.19041.1
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
-
- Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
20 answers
Sort by: Most helpful
-
Anonymous
2021-04-01T17:20:58+00:00 -
Anonymous
2021-02-09T19:44:45+00:00 Hey Greg,
Thank you for helping me out. This is so important I get this installed so that I could continue work. I really appreciate it.
I tried the first 2 methods you've proposed but nothing changed.
I also tried these methods I found on youtube again nothing.
https://youtu.be/JyMPISNL8qE
https://youtu.be/2f-YDm3OW7kAlso, I'm not sure if this is worth noting but when I try to download the program sometimes is changes my entire screen. It kind of zooms in. Here's a photo of what I mean. It goes away after I get to the point where it doesnt let me install.
Again, thank you for your help. I truly appreciate your guidance through this very frustrating situation.
-
Anonymous
2021-04-02T19:01:53+00:00 Yes, I was referring to the MSI file in that's extracted to the %temp% folder during installation of the .exe file. I didn't fully install the .exe. I just simply opened it and let it do its initial run without completing the installation.
The key is to run the EXE on a computer that gets past the initial error "Windows Installer" Parameter Required error message box.
So basically... open the exe , but don't follow any of the prompts > browse to %temp% folder > copy MSI > close exe
-
Anonymous
2021-03-29T18:12:22+00:00 I had the same issue and was able to get it installed by using another computer to run the "DLS8Setup8.7.4.exe" then finding the MSI in the temp folder. Copied the MSI to the non-working computer and installed it like a charm. If you want the "DYMO Label.msi", I uploaded it to my Dropbox here: https://www.dropbox.com/s/i3c0nfyl7dhbpfd/DYMO%20Label.msi?dl=0
-
Anonymous
2021-02-09T04:20:01+00:00 Hi Ismael. I'm Greg, awarded MVP for eleven years, Volunteer Moderator, and Independent Advisor here to help you until this is resolved.
Right click task bar to open Task Manager. If necessary show More Details
On Details tab look for msiexec.exe, highlight to End Task.
Now try install or uninstall again.
If this doesn’t help you can try to Fix problems that block programs from being installed or removed: https://support.microsoft.com/en-us/help/17588/...
This can be symptomatic of corruption. I would go over this checklist to make sure the install is set up correctly, optimized for best performance, and any needed repairs get done: http://answers.microsoft.com/en-us/windows/wiki...
Start with Step 4 to turn off Startup freeloaders which can conflict and cause issues, then Step 7 to check for infection the most thorough way, then step 10 to check for damaged System Files, and also Step 16 to test a new Local Admin account. Then continue with the other steps to go over your install most thoroughly.
Feel free to ask back any questions, or report back results as you go.
_______________________________
Linked tutorial is from a trusted Microsoft MVP