Microsoft Works Should I Remove It What is Microsoft Works Microsoft Works is an integrated package software that was produced by Microsoft. Works is smaller, less expensive, and has fewer features than Microsoft Office or other major office suites. Its core functionality includes a word processor, a spreadsheet and a database management system. Microsoft Works has built in compatibility for the Microsoft Office document formats DOC and XLS, including, but not limited to, the ability of the Works Word Processor to open Microsoft Word documents and the ability of the Works Spreadsheet to open Microsoft Excel workbooks. Overview. The most common release is 9. The primary executable is named gtngstrtd. The setup package generally installs about 3. KB 7. 47,4. 39 bytes. Program details. URL support. Help link go. microsoft. Link. Id6. 83. 1Installation folder C WindowsInstaller6. B9. AFA 1. A5. B 4. FF A0. 2E AA6. C0. B2. FFUninstaller Msi. Exec. exe I6. D5. C4. 08 B0. 9A 4. B1. B8. D3. 93. F1The Windows Installer is used for the installation, maintenance, and removal. Estimated size 7. KBLanguage English United StatesFiles installed by Microsoft Works. Program executable gtngstrtd. Path C WindowsInstaller6. B9. AFA 1. A5. B 4. FF A0. 2E AA6. C0. B2. FFgtngstrtd. MD5 4. Additional files. MicrosoftR Infotech Information Storage System Library Microsoft Info. Tech Storage System Library. Microsoft R Infotech Technology Library Microsoft Info. Tech IR Local DLLHow do I remove Microsoft Works Quickly and completely remove Microsoft Works from your computer by downloading Should I Remove It, its 1. FREE and installs in seconds click the button below. Or, you can uninstall Microsoft Works from your computer by using the AddRemove Program feature in the Windows Control Panel. On the Start menu for Windows 8, right click the screens bottom left corner, click Control Panel, and then, under Programs, do one of the following Windows Vista78 Click Uninstall a Program. Windows XP Click Add or Remove Programs. When you find the program Microsoft Works, click it, and then do one of the following Windows Vista78 Click Uninstall. Windows XP Click the Remove or ChangeRemove tab to the right of the program. Microsoft Works Word Processor Windows 7' title='Microsoft Works Word Processor Windows 7' />Follow the prompts. A progress bar shows you how long it will take to remove Microsoft Works. OS VERSIONSWin 7 SP1 5. Win 8 0 USER ACTIONSUninstall it 1Keep it 9. GLOBAL RANKWindows. Which Windows OS versions does it run onWindows 7. Windows 7 Loader Slic Activation Free Download. Windows Vista. 34. Windows 8. 4. 6. 9Windows XP2. Windows 8. 1. 0. 0. Windows Server 2. Which OS releases does it run on Windows 7 Home Premium. Windows Vista Home Premiu. Windows Vista Home Basic. Microsoft Windows XP2. Windows 1. 0 Home. A word processor is a computer program that provides special capabilities beyond that of a text editor such as the WordPad program that comes as part of Microsofts. History. Microsoft Works originated as MouseWorks, an integrated spreadsheet, word processor and database program, designed for the Macintosh by exApple employee Don. Download Microsoft Word Free. Microsoft Word is definitely the best text editor around. Its different functions have turned into the. The familiar Word app lets you create, edit, view and share your files with others quickly and easily. It also lets you view and edit Office doc attached. Windows 7 Professional. Geography. 62. 2. United States. Which countries install it  United States. Germany. 7. 0. 6  United Kingdom. France. 4. 0. 1  Canada. Italy. 2. 0. 2  Netherlands. Spain. 1. 1. 6  Belgium. Sweden. 0. 9. 0  Australia. Brazil. 0. 6. 2  Mexico. Austria. 0. 5. 0PC manufacturers. What PC manufacturers OEMs have it installedHewlett Packard. Acer. 21. 0. 5Dell. Toshiba. 13. 3. 9Medion. Sony. 1. 5. 8Samsung. Gateway. 0. 8. 7GIGABYTE0. Microsoft Works Word Processor Windows 7' title='Microsoft Works Word Processor Windows 7' />Common models. HP Pavilion dv. Notebook. HP Pavilion dv. 7 Notebook. Dell Inspiron 1. 54. HP G6. 0 Notebook PC3. Convert-Microsoft-Works-to-Microsoft-Word-Step-5.jpg' alt='Microsoft Works Word Processor Windows 7' title='Microsoft Works Word Processor Windows 7' />Hewlett Packard Compaq Pr. Dell Inspiron 5. 30. About Microsoft. Microsoft Corporation develops, manufactures, licenses and supports a variety of products and services related to computing. Publisher URL www. This isnt an authoritative answer Ive just had this problem, sifted through the initial bogus media coverage, found a solution, and started speculating on the real cause. Heres a workaround for the problem, though this company mis diagnosed the problem it wasnt an ACL problem. This fix is opaque and comes from a third party, but it fixed the problem for me http www. Black Screen woes could affect millions on Windows Vista and XP. Note their fix is an exe and they dont tell you what it does. I appreciate that they are helping, but they should fully disclose their fix so at least advanced users can have confidence in their good intentions. Heres a better possible reason for why the problem occurred a registry key telling Windows which shell to run on login was corrupted a REGSZ key was missing a 0. Sounds somewhat plausible, but the fishy part is what caused that http www. Windows Black Screen Root Cause. My symptoms observations I ran into this problem on a Win. Windows Vista Ultimate. I log in, get a black screen, and Windows never proceeds to setting up my desktop, etc ie, Windows never launches explorer. Running the fixing tool from Prevx did solve the problem, however their diagnosis for the cause of the problem was wrong their initial hypothesis was the ACLs were incorrect and implied Windows Update patches broke it, but that was wrong. They followed up with the non null terminated string hypothesis. Before running Prevxs tool, the registry key existed, Reg. Edit visually displayed the expected value explorer. ACLs were fine.   Yet, of course, I couldnt successfully log in. My pure speculation about the cause So if the missing 0 hypothesis is correct, and if the Prevx tool deletes recreates the value in the registry key, obviously that should fix the problem. FYI look at the MSDN docs for Reg. Set. Value. Ex for a note about the lp. Data parameter needing a 0. But that doesnt explain how the value got messed up in the first place  I dont go around removing terminating zeros from REGSZ values for fun nor profit. Sounds like either random corruption, or more likely, something wanted to run something when Windows boots then incorrectly undid their change to the registry. I saw that some MS security folks suggested this could be caused by malware http blogs. Operating under that hypothesis, I ran Forefront on Wednesday using the current signatures, but it didnt report anything. That may not spot a novel virus or rootkit, of course. Another wild guess perhaps the act of installing certain classes of patches could cause the problem, due to a hypothetical bug in Windows Update. Windows Update does something on boot up to configure patches, and it looks like this happens after login but before Explorer is running. Perhaps Windows Update itself could be editing this registry key to replace the shell with another program that configures patches or options to explorer. If thats how it works which is a big guess, then maybe when WU restores the registry key value to explorer. Win. 7.   Of course, I would have expect to see a bad value for this reg key in Reg. Edit if this were the case. I didnt perhaps there were some unprintable characters in the string, or Ive empirically shot down my own wild guess. Note my problem occurred on a Windows 7 Ultimate machine that was upgraded from Vista Ultimate. Perhaps something during upgrade may have introduced some registry corruption that didnt show up until another value in the registry was changed later  BTW, to confirm the fix narrow down this fix, perhaps someone w a broken machine can reboot into Safe Mode, run Reg. Edit, delete HKEYLOCALMACHINESoftwareMicrosoftWindows NTCurrent. VersionWinlogonShell then recreate the Shell key as a REGSZ key, with the value explorer. If that works, that could help confirm the cause and allow us to give standalone instructions for a fix that we can have more confidence in as opposed to telling people to run an exe from a third party.