Microsoft Office 2003 Basic Edition English (s55-00066) for PC Logo

Related Topics:

A
Anonymous Posted on Nov 05, 2013

Fix for wordlr.cab file for office 2013 - Microsoft Office 2003 Basic Edition English (s55-00066) for PC

Add Your Answer

×

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

0helpful
1answer

Why cant i use Office or word & when i try to reinstall or fix it ?

Somtetimes happens. If your copy is legal, ask your provider
0helpful
2answers

Change default font in word 2013

Click File > Options > General. Change the default font in "When creating new workbooks"

change-default-font-in-word-2013-vqyaikg4tgyrgzrpqfvwuo5d-4-0.png
0helpful
1answer

My setup file is in D drive not in CD/DVD...

Very easy to install microsoft 2013 and it works 100%,just only search @@@windows 8.1 key sale@@@ on bing.
0helpful
1answer

Office pa561401 cab

You can download the same version of office from any torrent website then run the setup to apply fixes to the errors.
0helpful
1answer

Setup cannot find proplus.ww owow64ww.cab

How to fix - Setup cannot find ProPlus.WW\ProPsWW2.cab


When you receive the error "Setup cannot find ProPlus.WW\ProPsWW2.cab" it might mean the MD5 checksum the install was expecting and the one on the actual file do not match. Here's how I fixed the issue.
First let me explain in simple terms what the MD5 is. MD5 is an algorithm that is used to verify data integrity. If anything in the file changes the MD5 will also change so it's a way for the program to check the integrity of the file.

The MD5 file is kept in the setup file of the proplus.ww folder. Open it with notepad and find the section that looks similar to the following **the numbers after "MD5 =" is what you need to be concerned with. Also remember that your numbers may differ. **


<LocalCache DownloadCode="{90140000-0011-0000-0000-0000000FF1CE}" SkuComponentDirectory="ProPlus.WW">
<File Id="Office64WW.xml" MD5="899A7D743D01852EBD036B465D1EF181" Size="4685" RelativeCachePath="Office64WW.xml" RelativeSourcePath="Office64WW.xml"/>
<File Id="Office64WW.msi" MD5="43B44C38BE513D9589ECAC7129DDC7C3" Size="3025408" RelativeCachePath="Office64WW.msi" RelativeSourcePath="Office64WW.msi"/>
<File Id="OWOW64WW.cab" MD5="E1E97F01F4292B89953204557A043C7D" Size="23865400" RelativeCachePath="OWOW64WW.cab" RelativeSourcePath="OWOW64WW.cab"/>
<File Id="ProPlusWW.xml" MD5="146CA2B8E1559F81E8DF6A3AED949E2A" Size="17252" RelativeCachePath="ProPlusWW.xml" RelativeSourcePath="ProPlusWW.xml"/>
<File Id="ProPlusWW.msi" MD5="F7DCCD578605F72AEEED775C9EB40AB8" Size="24809472" RelativeCachePath="ProPlusWW.msi" RelativeSourcePath="ProPlusWW.msi"/>
<File Id="ProPsWW.cab" MD5="3EA469E81A6064AE4BEFE4A9ACF36A9D" Size="149278843" RelativeCachePath="ProPsWW.cab" RelativeSourcePath="ProPsWW.cab"/>
<File Id="ProPsWW2.cab" MD5="86BEB0B6A2E76E95E580615185C06B04" Size="197934115" RelativeCachePath="ProPsWW2.cab" RelativeSourcePath="ProPsWW2.cab"/>
<File Id="setup.exe" MD5="4D92F518527353C0DB88A70FDDCFD390" Size="1100664" RelativeCachePath="setup.exe" RelativeSourcePath="..\setup.exe"/>
<File Id="osetup.dll" MD5="FCC38158C5D62A39E1BA79A29D532240" Size="5789544" RelativeCachePath="osetup.dll" RelativeSourcePath="osetup.dll"/>
<File Id="ose.exe" MD5="9D10F99A6712E28F8ACD5641E3A7EA6B" Size="149352" RelativeCachePath="ose.exe" RelativeSourcePath="ose.exe"/>
<File Id="pkeyconfig-office.xrm-ms" MD5="3DCFF1DCDEB1B837EC8F13351C8A92AC" Size="715834" RelativeCachePath="pkeyconfig-office.xrm-ms" RelativeSourcePath="pkeyconfig-office.xrm-ms"/>
<File Id="PidGenX.dll" MD5="7F120AAD20ECAE1EA421083F26611519" Size="1248016" RelativeCachePath="PidGenX.dll" RelativeSourcePath="PidGenX.dll"/>
<File Id="Setup.xml" MD5="" Size="" RelativeCachePath="Setup.xml" RelativeSourcePath="Setup.xml"/>
</LocalCache>
Next you will need to download and install an MD5 checker. I'll leave the process of how to use the MD5 to you to learn but it's pretty simple.

Next run the MD5 checker on the file/s that produce the errors during install. *there may be more than one*

Now there are 2 ways to work around this - If the MD5 on the checker did not match the MD5 in the file it probably means the file is corrupted so your best bet is to download the software again or get another disk.

Another less recommended way is to copy/paste the MD5 from the checker into the file (remember to make a backup of your setup file before) then save it and run the install again. This fools the installation process into verifying that your installation files are all OK.

Good luck!!
8helpful
4answers

SKU001.CAB

i want file which name is sku001.cab
Not finding what you are looking for?

715 views

Ask a Question

Usually answered in minutes!

Top Microsoft Computers & Internet Experts

Grand Canyon Tech
Grand Canyon Tech

Level 3 Expert

3867 Answers

k24674

Level 3 Expert

8093 Answers

Brad Brown

Level 3 Expert

19187 Answers

Are you a Microsoft Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...