Upsourcer: Slipstream patches for Office 2007/2010/2013/2016 and rebuild setup source files

Some Office 2010 update(s) include(s) mso.dll that is not compatible with Windows XP. Someone modified the last version of Office 2010's mso.dll (detail: change imports) to make it work on Windows XP, but not sure if @abbodi1406 will want to add it.

P/S: Such mso.dll modification is unavailable for x64.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thanks for the update. The new version of Office 2013 MSI Upsourcer works very well. Tested, the previous error no longer occurs.

 

I found the reason for the previous error. VirtualBox Guest Additions 7.0.8 is very unstable with frequent memory leaks. I can successfully run Office 2013 in VirtualBox without Guest Additions installed. I tested Win7 Win8.1 Win10 in the virtual machine, and they are all the same.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Install the original unmodified Office 2013. Regardless of whether Guest Additions is installed or not, no errors appear.

 

All right. I put MSPs into the Updates directory. After testing, it still doesn't work properly. It turned out to be a problem with Office itself. Or is it incompatible with Guest Additions?

 

You need to login to view this posts content.

 

Office 2013 x86 also has the same problem as x64.

Use MS official method. Putting MSPs into the Updates directory also gives errors. Is it a problem caused by some MSP patch? Because Office 2013 before integrating MSP can run normally anyway.

 

The "black background" error that appeared before. If you leave it still for a period of time, below is the error that occurs when I open Word. Other Office components are similar.

Error 1

Code:

Insufficient memory or disk space.

Error 2

Code:

Word fails to raise event.

Error 2, Show Help

Code:

This error is usually due to insufficient memory or low disk space. It also occurs when the default Word template (normal.dotm) is corrupt, when the VBE6.DLL file is the wrong version, or when permissions to the TEMP folder on a server share do not allow access to the folder by the user.
Low memory or disk space can be solved by either closing unused applications, removing unused programs or files from your hard drive, or by adding RAM or a larger hard drive. In some cases, a memory leak may have occurred and is consuming RAM without your knowledge. If you suspect that a memory leak is the problem, shutdown Word and VBA and restart the computer.
Rename the normal.dotm file and then restart Microsoft Office Word. When you exit Word, Word will build a new normal.dotm file. If you have a backup of normal.dotm, you can replace the defective file with the backup copy instead of having Word repair the file.
If the VBE6.DLL is not the correct version, replace it.
If your network permissions are inadequate for access to a TEMP folder on a server share, consult the administrator and determine if the permissions can be changed. If they cannot, redirect VB to use a local TEMP folder.

 

You need to login to view this posts content.