Microsoft Works 6 9 File Converter For Mac
Microsoft works 6 9 file converter free download - MS Works Converter, Prism Free Video File Converter, MS Works Wks and WDB Files Budget Converter, and many more programs. The Microsoft Works 6-9 File Converter is an optional download that allows Microsoft Office applications to open, edit, and save files in the Works Word Processor file format supported by the Works versions 6, 7, 8, and 9.
Security Bulletin
Vulnerability in Microsoft Office Could Allow Remote Code Execution (2639185)
Published: April 10, 2012 Updated: April 25, 2012
Version: 1.1
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft Office and Microsoft Works. The vulnerability could allow remote code execution if a user opens a specially crafted Works file. An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
This security update is rated Important for Microsoft Office 2007 Service Pack 2, Microsoft Works 9, and the Microsoft Works 6–9 File Converter. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by deprecating the vulnerable Microsoft Works converter. Customers should use the latest version of the Microsoft Works converter, which is not affected by the vulnerability. After the update is installed, customers with the deprecated Microsoft Works converter, who have not already downloaded the latest version of the Microsoft Works converter, will be prompted when attempting to open a Works file with instructions on how to download the latest version of the Microsoft Works converter. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates from Microsoft Update and install this update manually. For information about specific configuration options in automatic updating in supported editions of Windows XP and Windows Server 2003, see Microsoft Knowledge Base Article 294871. For information about automatic updating in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, see Understanding Windows automatic updating.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. None
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Office Software | |||
| [Microsoft Office 2007 Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=fbf24cc6-89e1-48dd-bb83-23eed30195e1) (KB2596871) | Remote Code Execution | Important | KB969559 in [MS09-024](http://go.microsoft.com/fwlink/?linkid=128104) replaced by KB2596871 |
| Other Software | |||
| [Microsoft Works 9](https://www.microsoft.com/download/details.aspx?familyid=94e17a66-cf09-4314-89ec-53deadabfa66) (KB2680317) | Remote Code Execution | Important | KB2431831 in [MS10-105](http://go.microsoft.com/fwlink/?linkid=147425) replaced by KB2680317 |
| [Microsoft Works 6–9 File Converter](https://www.microsoft.com/download/details.aspx?familyid=4605f684-6314-4758-adeb-2a8810dfc8d1) (KB2680326) | Remote Code Execution | Important | KB968326 in [MS09-024](http://go.microsoft.com/fwlink/?linkid=128104) replaced by KB2680326 |
| Office and Other Software |
|---|
| Microsoft Office 2003 Service Pack 3 |
| Microsoft Office 2007 Service Pack 3 |
| Microsoft Office 2010 (32-bit editions) |
| Microsoft Office 2010 Service Pack 1 (32-bit editions) |
| Microsoft Office 2010 (64-bit editions) |
| Microsoft Office 2010 Service Pack 1 (64-bit editions) |
| Microsoft Office 2008 for Mac |
| Open XML File Format Converter for Mac |
| Microsoft Office for Mac 2011 |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2 |
| Microsoft Office Compatibility Pack Service Pack 3 |
Frequently Asked Questions (FAQ) Related to This Security Update
I have Microsoft Office 2007 Service Pack 3 installed. If it is not affected, why am I being offered this update?
Although the vulnerability described in CVE-2012-0177 does not affect Microsoft Office 2007 Service Pack 3, the update mechanism offers the update because it detects a lower version of the files on the system as compared to those in the update package.
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
What is the Microsoft Works 6-9 File Converter?
The Microsoft Works 6-9 File Converter is an optional download that allows Microsoft Office applications to open, edit, and save files in the Works Word Processor file format supported by the Works versions 6, 7, 8, and 9.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle website.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the April bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Office WPS Converter Heap Overflow Vulnerability - CVE-2012-0177 | Aggregate Severity Rating |
|---|---|---|
| Office Software | ||
| Microsoft Office 2007 Service Pack 2 | **Important** Remote Code Execution | **Important** |
| Other Software | ||
| Microsoft Works 9 | **Important** Remote Code Execution | **Important** |
| Microsoft Works 6–9 File Converter | **Important** Remote Code Execution | **Important** |
Office WPS Converter Heap Overflow Vulnerability - CVE-2012-0177
A remote code execution vulnerability exists in Microsoft Office Works File Converter. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0177.
Mitigating Factors for Office WPS Converter Heap Overflow Vulnerability - CVE-2012-0177
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- In a web-based attack scenario, an attacker could host a website that contains a specially crafted file that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website, and then convince them to open the specially crafted file.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
- The vulnerability cannot be exploited automatically through email. For an attack to be successful, a user must open an attachment that is sent in an email message.
Workarounds for Office WPS Converter Heap Overflow Vulnerability - CVE-2012-0177
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Do not open Works files that you receive from untrusted sources or that you receive unexpectedly from trusted sources
Do not open Works (.wps) files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
FAQ for Office WPS Converter Heap Overflow Vulnerability - CVE-2012-0177
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Microsoft Works converter does not properly validate the .wps file format when parsing a specially crafted file.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted .wps file with an affected version of Microsoft Office.
In an email attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by convincing the user to open the file.
In a web-based attack scenario, an attacker would have to host a website that contains a specially crafted Works file that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers that have the affected versions of Microsoft Office or Microsoft Works installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update addresses the vulnerability by deprecating the vulnerable Microsoft Works converter. Customers should use the latest version of the Microsoft Works converter, which is not affected by the vulnerability. After the update is installed, customers with the deprecated Microsoft Works converter, who have not already downloaded the latest version of the Microsoft Works converter, will be prompted when attempting to open a Works file with instructions on how to download the latest version of the Microsoft Works converter.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for 'security update.'
For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see Check for software updates automatically.
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, 'MS07-036'), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Microsoft Office 2007 Service Pack 2 | Yes |
| Microsoft Works 9 | Yes |
| Microsoft Works 6–9 File Converter | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|
| Microsoft Office 2007 Service Pack 2 | Yes | Yes |
| Microsoft Works 9 | Yes | Yes |
| Microsoft Works 6–9 File Converter | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS website.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Note If you have used an Administrative Installation Point (AIP) for deploying Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.
Office Administrative Installation Point
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system.
- For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see Microsoft Knowledge Base Article 922665.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image. - For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 902349.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, Distributing Office 2003 Product Updates. - For creating a network installation point for supported versions of Microsoft Office, see Create a network installation point for Microsoft Office.
Note If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for Microsoft Office, visit the Windows Server Update Services website.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
Important note for Office 365 subscriptions: After September 22, 2016, Office 2011 for Mac is no longer available for installation with an Office 365 subscription.This doesn't affect one-time purchases of Office for Mac 2011 such as, Office Home and Student, Office Home and Business, or Office Professional. This article is for Office for Mac 2011. Are you using Office on PC? See Using product keys with Office 365, Office 2016, or Office 2013. Where do I find my Office for Mac 2011 product key? Once you have your product key, see Activate Office for Mac 2011. When you install or reinstall Microsoft Office, you are prompted to enter the product key. 
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Office 2007 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | works6322007-kb2596871-fullfile-x86-glb.exe /passive |
| Installing without restarting | works6322007-kb2596871-fullfile-x86-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| RemovalInformation | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2596871 |
| Registry Key Verification | Not applicable |
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Works 9 and Works 6–9 File Converter
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | For Microsoft Works 9: Works9_KB2680317_en-US.msp /passive |
| For Microsoft Works 6–9 File Converter: Works9Conv_KB2680326_en-US.msp /passive | |
| Installing without restarting | For Microsoft Works 9: Works9_KB2680317_en-US.msp /norestart |
| For Microsoft Works 6–9 File Converter: Works9Conv_KB2680326_en-US.msp /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | For Microsoft Works 9, see Microsoft Knowledge Base Article 2680317 |
| For Microsoft Works 6–9 File Converter, see Microsoft Knowledge Base Article 2680326 | |
| Registry Key Verification | Not applicable |
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| /quiet or /q[n b r f] | Quiet mode, no user interaction or /q[n b r f] sets user interface level: n - No user interface b - Basic user interface r - Reduced user interface f - Full user interface (default) |
| /passive | Unattended mode - progress bar only. |
| /norestart | Do not restart after the installation is complete. |
| /l[i w e a r u c m o p v x + ! *] <LogFile> | Enables logging. Options: 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>. |
To view a Microsoft Works .wps file in Microsoft Word, you need a converter that enables Microsoft Word to view the files.
Microsoft provides a free file called WorksConv.exe that is compatible with Microsoft Word 2000 and later, allowing you to open Microsoft Works 6.0 to 9.0 documents.
To open older .wps documents created with Microsoft Works 4.0 or 4.5, Microsoft provides Wks4Converter_en-US.msi.
We recommend downloading and installing both of these files.
TipMicrosoft Word 2013 is capable of opening Microsoft Works 6.0 to 9.0 documents by default. However, you will still need to download and install the Wks4Converter_en-US.msi file to open Microsoft Works 4.0 or 4.5 documents.
Once these files are downloaded, follow the steps listed below.
- Close any open Microsoft Word windows.
- Double-click the WorksConv.exe file and follow the prompts to install it. Then, double-click the Wks4Converter_en-US.msi file and follow the prompts to install it as well.
- After installing both files, open Microsoft Word.
- In Microsoft Word, click File and then click Open. If there is no File menu, click the Microsoft Office button in the top left of the Word window, then click Open.
In Word 2013, after clicking the Open option, you need to select Computer, then click Browse.
In Word 2016 and later, after clicking the Open option, you need to click Browse.
- In the Open window, in the File type drop-down menu or the unlabeled drop-down menu next to the File name text field, you should now have two or three options: Works 4.x (*.wps), Works 6-9 Document (*.wps), and Works 6.0 (*.wps).
- Select the appropriate version of Works for the file you are opening. If you're not sure which version your Works file is, try the Works 6-9 Document (*.wps) option first.
- Browse to the location of the Works file you want to open, select the file, then click Open.
After I open the file, it's not formatted properly
Depending on how the Microsoft Works file was created and formatted, you may be able to open it, but it looks strange because the formatting was not converted properly. If this occurs, try opening the file as a different Works version. If this does not work, you'll have to change the formatting manually in Word if you want it to display correctly.
Saving the file as a Word file
If you want to continue to use this file or want to make it compatible with Microsoft Word, follow the steps below.
- After the file is opened and edited, click File and choose Save As. If there is no File menu, click the Microsoft Office button in the top left of the Word window, then click Save As.
- In the Save As window, select the location you want to save the file.
In Microsoft Word 2016 and later, you need to click the Browse option after clicking the File tab to open the Save As window.
- Type a name for the file if you want to change it.
- In the Save as typedrop-down menu or the unlabeled drop-down menu next to the File name text field, make sure to select Microsoft Word (*.docx).
- Click Ok or Save when done.
Additional information
Microsoft Works 6-9 File Converter
- See our Microsoft Word and Microsoft Works definitions for further information and related links.