Office 2013-2016 C2R Install Install Lite 6.0.3 Test Serial Key

0 views

Skip to first unread message

Message has been deleted

Sibyl Piccuillo

unread,

Jul 10, 2024, 7:32:13 AM7/10/24

to nautechchondcrib

I'm aware of this question: C#: How to know whether certain Office 2003 or 2007 application is installed?, but don't know how to check and combine multiple conditions in WiX. I totally can't come up with anything beyond what's in the above question...

Office 2013-2016 C2R Install Install Lite 6.0.3 Test Serial Key

Download File https://lpoms.com/2yLRWH

I would not do that. There are too many options how office can be installed nowadays. "Office 365" version that is installed with ClickToRun and not MSI as an example (and may use different registry keys), 32 vs 64 bit options, etc. User can even install office after installing your tool, or update office version later.

Everything depends on which Office editions you need to support. There are Click2Run editions of MS Office that don't add the usual or necessary windows registry keys. In that case you need to have a special case for that, for example, if your add-in is for Outlook, you could check the following path in the windows registry:

I guess that the Office 365 page will just offer a download for the 2016 version now or is there a trick to make it install the 2013 version? I can test the Office 365 support through a work account, but I guess I need to find a 32-bit copy of the 2013 version for that.

Excellent job!! This sure will attract many with Office 365 subscriptions. I think it should be with a great marketing campaign. Something like "Run your Office 365 in Linux". Also OneDrive should work also for a complete experience.

Office 365 does have a way to let you install Office 2013 - you can
get an installer for Office 2013 by logging into your Office 365
account and downloading one.
Thanks! It seems you were just ahead of me when I posted that URL in the nightly forums! I understand that this installer also works (not just the offline one)?

Pleas check if you have installed the correct Driver. This post may help. Maybe you need the Office 365 runtine instead the 2013 runtime. You can download it here: -us/office/download-and-install-microsoft-365-access-runtime-185c5a3...

We all know that the latest compatible version of Office with Vista is 2010. I think that you can install Office 2013 in Vista by editing some EXE and DLL.

The main error comes from SETUP.EXE that comes out a window that says "This program requires a more recent version of Windows", I think that using hexadecimal editors you can remove that Windows version detector.

If also another thing like cheating the installer with which you are using Windows 7 and not Vista for open the Office 2013 Installer.

I know Office 2013 is ugly, but I'm doing tests in Vista, despite everything I think that editing setup.exe and kernel32.dll is enough, since Vista is NT6.0 and 7 is NT6.1

I wonder, how do you know about the K32GetProcessImageFileNameW error if the installer blocks any system prior to Windows 7?

I do not understand how this is used, I'm using Windows Vista x64 and when I choose Windows 7 and SP1, when I give it to Fake Reg, it still shows that damn window that requires a newer version of Windows. Another thing that could help the program is to use Chrome 41+ as it enables the Aero Glass and does not show the annoying message that it will not be more compatible with XP and Vista.

Hello everyone, excellent news, now I have IDA Pro and it no longer appears that it requires a recent version of Office 2013, since I modified the cave code In Windows XP x86 it works, in Vista (both artitectures) I imagine that too.

How to install Office 2013 on Vista
1- Have a copy of Office 2013 64-bit handy (The latest extended kernel is needed, x86 is useless)
2- Copy to the desktop in a new folder the root of your copy of Office 2013
3- Copy the ProPlus.WW.en-US folder to the desktop (the name may vary due to the language/edition of the copy), this is important since the Office installer detects the edited files and the installer of this folder needs to be edited.
4- In the folder copied to the desktop open ProPlus.WW.msi with Orca, go to InstallExecuteSequence and remove AbortMsi (it blocks the installation outside of setup.exe that verifies the files), then in Components change all Conditional VersionNT >= 601 by VersionNT >= 600.
5- Replace gdiplus.dll with the one from Windows 7, this is the path in the system:

8- Open ProPlus.WW.msi and after installation the Office 2013 suite should appear in the start menu, but it is not enough!
9- Go back to group policies and disable rollback, but keep osver.ini
10- In the root folder of Office 2013 the only change we will make is to delete the update or updates folder, they cause bugs when installed
11- Open the setup.exe of the normal Office 2013 installer and customize it to your liking (it should install successfully, if an error appears, reboot the system)
12- Open Word 2013 (it can be any program in the suite except Visio, Lync, InfoPath or Outlook) to configure Office 2013
13- The programs of the Office 2013 suite will need to be detected at all times as Windows 7 or an annoying Windows Installer dialog will appear configuring each time the program starts:

We have partly killed the obsolescence imposed by M$ in Vista, which only received two versions of Office. Almost the entire suite works perfectly under Vista, except for Lync or InfoPath that I don't find useful, Outlook and the lack of dependencies in advapi32.dll.
In the usual programs like Word, Excel or Powerpoint I can do anything without problems as if I were in Windows 7 or 8.

The only way I can PDF multiple Word Documents is to go into each one individually in Word (Office 2013) and save as PDF, which is really tiem consumign when I have 50 word documents. I have tried disabling the PDF add-on for Word - and same error. Also same error when I re-enable the addo-on.

Folks, I had this same problem on two separate pc's. It took me a couple of hours to figure out a way to work around it. Specifically, using Windows 7 and 8.1, Word 365, and Adobe writer subscription or whatever, when I would right click on the word document and convert to pdf or combine as a pdf, it would return the error. The other methods would work fine, but since I routinely compile word documents to a single pdf to circulate drafts, this was an unacceptable workaround. There was no sup

I'd like to know why too. This is absolutely ridiculous that Adobe has an issue, you are not fixing it, and Staff is not posting the solution, but emailing it. Why not post it so everyone can see it and fix your darn program!

In the fall of 2021, both MS and Adobe released buggy upgrades to their software which caused many crashes like those described here. It's been common over the years as both companies' updates leapfrog over each other.

Both MS and Adobe have upgraded since the Fall 2021 and hopefully everyone's software now can work together. But if not, check your versions against the official release notes for MS and Adobe, and see if the latest updates correct the problem:

If the problem still exists after updating both Office and Acrobat, then the detailed steps below should clear up the problems. They were given to my firm by various Adobe and MS engineers, back when we were system integrators. We learned the hard way: don't skip any of these steps, and Office must be installed and updated before Acrobat is installed.

I am still having this issue on multiple workstations. If there is a tool that can be provided to fix this issue it would be greatly appreciated, or even steps to address it. This is a growing problem and there appears to be no publicly available solution for this.

I'm getting error when right clicking Word doc and selecting Convert to Adobe PDF. It works if I open the Word doc in Word and create manually but customers have hundreds of docs they need to convert in Windows Explorer

Bottom line, the only way I have solved the problem is to uninstall microsoft office, and then re-install microsoft office with the adobe product still on the pc. In other words, install word after adobe. Then, in word, go to file - options - add ins and make sure the acrobat pdfmaker office com addin is active. Full disclosure, this last step may not be necessary, as it may have resulted from my previously making it inactive when trying to figure this issue out. Also, my assistant had previously attempted to reinstall adobe, and that did not help the problem. So it appears to be a matter of installing word after adobe.

We currently deploy Office 2016 on campus because it's relatively hands-off with our KMS activation server. We would like to move to O365 Office Suite but a major concern is we don't want professors or students to have to sign into Office for activation just to use it. We have several classrooms that would be this way and also labs that many users signing in daily. My question is does anyone have experience deploying O365 in a similar manner using device based activation? Or is there another way since that process seems overly cumbersome. My plan is to deploy it as part of an image post install task with the KACE SDA. Any advice would be welcome.

The setup took some time to get configured, but once it was done, it works very well. We also prefer it because it always installs the latest version from Microsoft, so when we deploy systems on the K2000, Office installs as a post-install task and we know the user is getting the latest version (based also on what deployment ring they are in).