PRocesses: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9
Dlls: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9
Popular: svchost.exe | csrss.exe | rthdcpl.exe | spoolsv.exe | mrt.exe | lsass.exe | Home | Manufacturers


Why doesn't WINWORD.EXE quit after Closing the document from Delphi?

I managed to distill one of the underlying issues rooted in my question How to trace _AddRef / _Release calls for OLE Automation objects in the unit below.

I'll answer this answer too, just in case anyone else bumps into this.

The question: with the below code, why doesn't WINWORD.EXE always quit (sometimes it does quit).

The unit can probably be trimmed down even more.

unit Unit2;


Winapi.Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls,
Forms, Dialogs, StdCtrls,

TForm2 = id(TForm)
WordXPFailsToQuitButton: TButton;
procedure WordXPFailsToQuitButtonClick(Sender: TObject);
FWordApplication: TWordApplication;
strict protected
function GetWordApplication: TWordApplication; virtual;
function GetWordApplication_Documents: Documents; virtual;
procedure WordApplication_DocumentBeforeClose(ASender: TObject; const Doc: _Document; var Cancel: WordBool); virtual;
procedure WordApplication_Quit(Sender: TObject); virtual;
property WordApplication: TWordApplication read GetWordApplication;
property WordApplication_Documents: Documents read GetWordApplication_Documents;

Form2: TForm2;



{$R *.dfm}

function TForm2.GetWordApplication: TWordApplication;
if not Assigned(FWordApplication) then
FWordApplication := TWordApplication.Create(nil);

FWordApplication.AutoConnect := False;
FWordApplication.AutoQuit := False;
FWordApplication.ConnectKind := ckNewInstance;
FWordApplication.OnDocumentBeforeClose := WordApplication_DocumentBeforeClose;
FWordApplication.OnQuit := WordApplication_Quit;
Result := FWordApplication;

function TForm2.GetWordApplication_Documents: Documents;
Result := WordApplication.Documents;
if not Assigned(Result) then
raise EAccessViolation.Create('WordApplication.Documents');

procedure TForm2.WordXPFailsToQuitButtonClick(Sender: TObject);
WordApplication_Documents.Add(EmptyParam, EmptyParam, EmptyParam, EmptyParam);
WordApplication.Visible := True;
WordApplication.ActiveDocument.Close(False, EmptyParam, EmptyParam);
WordApplication.OnQuit := nil;
WordApplication.OnDocumentBeforeClose := nil;
WordApplication.AutoQuit := True;
FWordApplication := nil;

procedure TForm2.WordApplication_DocumentBeforeClose(ASender: TObject; const Doc: _Document; var Cancel: WordBool);

procedure TForm2.WordApplication_Quit(Sender: TObject);


View Complete Forum Thread with Replies

Related posts for winword.exe

See Related Forum Messages: Follow the Links Below to View Complete Thread C# - WINWORD.exe
Winword.exe processes will not close on server
kill Winword.exe after the vbscript
WinWord.exe won't close
Check if WINWORD.EXE Process is Running?
How close Winword.exe in my application
c# interop winword.exe doesn't Quit()!
how to kill orphaned winword.exe in matlab
Winword.exe ignores parameters AFTER one parameter with quotes
c# MSOffice Interop Word will not kill winword.exe
how to close a winword.exe that runs in the background (Interop was used) [closed]
WinWord.exe won't quit after calling Word.Documents.Add - Word .NET Interop
Why doesn't WINWORD.EXE quit after Closing the document from Delphi?
How do I terminate WINWORD.EXE when used by classic ASP?
Close Winword.exe in my application depending on dialog box information

winword.exe: C# - WINWORD.exe

I am playing with Microsoft word document from ASP.NET/C# program.

My programs opens up word docs internally. using

app = new Word.Application();

it creates a instance of winword.exe process, I can see it in Task Manager.

even if I closes Doc using close() and app.quit(). it should kill the process. but this process doesnt get killed.

any idea how to kill this process programmatically.

winword.exe: Winword.exe processes will not close on server

Good day all
I have a bit of a head scratcher on my hands.
The following code runs on my server and it does work for what it is intended.

public void RenderWithData(string strcaseno, string strdocpath, string strdocsp, string stramnt)
Microsoft.Office.Interop.Word.Application appWord = new Microsoft.Office.Interop.Word.Application[];
string suffix = Convert.ToString(DateTime.Now.Minute + DateTime.Now.Millisecond);
string sourceFileName = System.Web.HttpCont

winword.exe: kill Winword.exe after the vbscript

When i run the below VB script i get the desired output as expected.

But, a new winword.exe process is ran, which i wanted to kill after the script ends.

Set Wshshell= CreateObject('Word.Basic')
WScript.Sleep 1500
Set wshshell = Nothing

set WshShell = WScript.CreateObject('WScript.Shell')
WshShell.Run 'mspaint'
WScript.Sleep 1000
Set wshshell = Nothing

Set Wshshell= CreateObject('Word.Basic')
WshShell.AppActivate 'Paint

winword.exe: WinWord.exe won't close

I am running into issues creating a Word document Word from Excel using

Set wordapp = CreateObject('word.Application')
Set letter = wordapp.Documents.Add

On first run it works fine, on second run it hangs. I think the issue is if I close the document I created using the Close Button in Word, it won't close WinWord.Exe. I think it has to do with whether I saved the document or not. How can I get around this?

I uninstalled/deactivated all of my Add-ins (I heard that co

winword.exe: Check if WINWORD.EXE Process is Running?

I've got a C# Winforms Application that processes queried data into Mail Merge documents. How can I check on application start-up to see if current user has a Microsoft Word Instance Open, and if so, alert them to close before proceeding?

winword.exe: How close Winword.exe in my application

I have two problem


When i started my app and opened word file i see 3 process winword.exe in taskmanager.
After i called 'close' function 1 process winword.exe closed.


When i called worddoc.close() or wordapp.quit() in destructor, i got exception 'COM object that has been separated from its underlying RCW cannot be used.'

this is my id

public id WordHelper
private object nullobj = System.Reflection.Missing.Value;

winword.exe: c# interop winword.exe doesn't Quit()!

I feed multiple docs to the below method and see winword.exe disapear as expected on over 15 diferente PCs running WinXP 32bit to Win8 64bit having Office 2000 onwards. On 1 nightmare PC that has Trend's Antivírus running, winword.exe (Always, every time) interrupts the loop with a 'File in Use' exception (turning Trends off allows it to work again). Any ideias to keep Trends on?

void loop()
Microsoft.Office.Interop.Word._Application app = new Microsoft.Office.Interop.Word.Applica

winword.exe: how to kill orphaned winword.exe in matlab

Running matlab R2010B on Windows 7 Enterprise

In matlab scripts, I save a bunch of results to a word file and then at the end, close and quit word. The code I use is:

WordFname = ['BatInfoDoc' sprintf('%0.3f',now) '.doc']; % serialnumbered filenames
WordFile = fullfile(pwd,WordFname);
WordApp = actxserver('Word.Application');
WordDoc = WordApp.Documents.Add;
WordApp.Selection.TypeText([title2 title3 title4 title5 title6]);

winword.exe: Winword.exe ignores parameters AFTER one parameter with quotes

My problem from word command-line-arguments space problem seems to be a specific winword.exe problem. says: MyApp.exe 'alpha with spaces' 'beta with spaces' ==> MyApp.exe, alpha with spaces, beta with spaces

This is not true for winword.exe.

winword.exe /alpha:1 /beta:2 ==> OK
winword.exe '/alpha:1 space' '/beta:2' ==> beta is missing?!
winword.exe /alpha:'1 s

winword.exe: c# MSOffice Interop Word will not kill winword.exe

I'm writing an application that needed a MSWord document parser.

I'm using Microsoft.Office.Interop.Word.Document to extract the texts from the documents, but even if i use doc.Close() the document, from taskManager i can see that winword.exe are not killed, and after parsing a couple dozens documents it eats up some much resources.

is close() the wrong method?

please help me and point me to the right direction on how to terminate these processes properly. =)


winword.exe: how to close a winword.exe that runs in the background (Interop was used) [closed]

i created a word doc in vb but the problem is each time my button is clicked it opens a new doc. i have tried the following code to terminate it after it fulfilled its
purpose but nothing seems to work and
i have search multiple sites but found no answer that helped
i used interop

my attempts to close the background winword.exe (objDoc is the the word doc )


winword.exe: WinWord.exe won't quit after calling Word.Documents.Add - Word .NET Interop

I'm running into the idic scenario where, when creating Word COM objects in .NET (via the Microsoft.Office.Interop.Word assembly), the WinWord process won't exit even though I'm properly closing and releasing the objects.

I've narrowed it down to the use of the Word.Documents.Add() method. I can work with Word in other ways without a problem (opening documents, modifying contents, etc) and WinWord.exe quits when I tell it to. It's once I use the Add() method (and only when adding a temp

winword.exe: Why doesn't WINWORD.EXE quit after Closing the document from Delphi?

I managed to distill one of the underlying issues rooted in my question How to trace _AddRef / _Release calls for OLE Automation objects in the unit below.

I'll answer this answer too, just in case anyone else bumps into this.

The question: with the below code, why doesn't WINWORD.EXE always quit (sometimes it does quit).

The unit can probably be trimmed down even more.

unit Unit2;


Winapi.Windows, Messages, SysUtils, Variants, Classes

winword.exe: How do I terminate WINWORD.EXE when used by classic ASP?

I have a user who has to use Microsoft Word 2007 to create and manipulate word documents in his ASP web application. I'm well aware of the 'Considerations for server-side Automation of Office' KB article and the many third party components available to do this kind of thing, but they've gone a fair bit down this road already.

The problem he's having is that the WINWORD.EXE process never terminates even though he calls Quit on the application object.

For example:

Set objWord

winword.exe: Close Winword.exe in my application depending on dialog box information

I have a third party software that starts a word process.

I have no problem finding the process with:


When the process starts a dialog box appears with different kind of informations for the user depending on if the word doc has a active macro, is write protected etc.

My question is: How can I access the header infomation of the dialog box so I can perform different actions according to the informations provided in the dialog box head

excel.exe: Orphaned object keeping Excel.exe in Task Manager?

I have this script that I'm working on, and am soooo close to having it done, but have a slight issue. I am getting the common Excel.exe lingering in the Task Manager issue, and having a hard time resolving it. The code below worked fine, until I added the lines marked 'worksheet input'. What I am trying to do, is route data from a PC DMIS program (outside of Excel), into separate worksheets based on the operator input box. If I take out the lines I added (worksheet input), it runs fine, and Exc

taskmgr.exe: Is it possible to add functionality to Vista/7 taskmgr.exe?

I was wondering if anyone knew whether taskmgr.exe in Windows Vista/7 was extend-able via a plugin system.

I found this, but this is limited to XP,2k3 and he specifically states he didn't know about vista's and seven's.

conhost.exe: How would I redirect console output for all applications a application I launch using a Process

I'm redirecting a application which spawns a conhost.exe. How would I attach to that and redirect the output/input?

csrss.exe: What does the csrss.exe process do?

What is the purpose of the csrss.exe (Client/Server Runtime Server Subsystem) on Windows?

Maybe someone could give a good explanation or pointers to documentation? Unfortunately Google results are pretty noisy when searching a core process of Windows.

The reason I'm asking is that I got a BSOD from my service application which seems to be related to the csrss.exe process, at least this is what the analysis of the memory dump shows:



defrag.exe: Process.Start in WindowsSystem32 folder

Trying to launch a file located in System32 as administrator but it keeps telling me it doesn't exist.

Error: System can't find specified file
Build Target Platform is: x86.
Current OS: Windows 8.1 x64. I'd rather not have 2 different .exes for a 32 and 64 bit os.

p.StartInfo.Verb = 'runas';
p.StartInfo.FileName =
//above points to c:windowssystem32defrag.exe

rundll32.exe: C# DLL loaded for exe-application is not found when launching similar DLL by rundll32.exe

I have built a C++/CLI DLL that is a wrapper for some .NET C# DLL. As a sample application I have built a simple project for exe-application based on WindowsForms GUI. It works fine with my C++/CLI library and the mentioned .NET C# DLL. But if I build another C++ DLL, which substitutes this sample exe-application, it doesn't succeed to load the .NET C# DLL, although it is located in the current Windows path. The following exception is occurred when trying to call some function from this C# code:

dw20.exe: Need emergency help with dw20.exe process? [closed]

recently I have deployed application to production windows server 2008.

after 10-20 min, starts dw20.exe process ( error reporting shim), which takes almost all CPU available which cause to very slow response of my application.

No error no exception in Event Viewer.

I right clicked on the dw20.exe process and created the dump file to analyze what causing the issue.

Then I opened this file in WidDbg. run command .loadby sos mscorwks and get Unabl

sidebar.exe: Reliably detecting OS architecture in a Windows Desktop Gadget

I have some Javascript code that will programmatically register an COM interop assembly by writing all the necessary keys and values to the registry. An older version of this COM object was written in VB6 and didn't work correctly on x64 versions of Windows unless the user manually ran the x86 sidebar.exe, so some of our users would have switched to using the x86 sidebar.exe for the COM object to work.

In short, I need to correctly detect the architecture of the operating system currentl

mmc.exe: CreateProcessWithLogonW and mmc.exe

I wrote a program, that should work like RunAs. It works fine, but i have one problem with it. If i want to run for example compmgmt.msc, then i should run mmc.exe and compmgmt.msc as it's parameter. Computer Management will open, but not under the user as i want to run it. It will run under that username who is logged in. Can someone tell me why is that, and how can i correct it? Here is my code :

void createproc(
wchar_t * user,
wchar_t * domain,

regedit.exe: How to detect Java is installed via REGEDIT.exe from a batch file?

I am looking for a batch file snippet that somehow reads the Windows registry and detects which Java JDK is on a Windows system and then asks the user which one they want to use and remembers the choice.

Here is what I have so far... needs some modifications. This script only finds the first JDK... it doesn't handle multiples.

@echo off
SETLOCAL EnableDelayedExpansion
:: findJDK.bat
start /w regedit /e reg1.txt 'HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Development Kit'

EUROBYTE TOOLS - cleans and speeds up your computer

You know it: the longer you own your computer, the slower it runs and the more often the stucks.
Can I change it?
Of course Yes.

Try EUROBYTE TOOLS, program, that cleans and speeds up thousands of computers around the world.
It's quick, automatic and effortless.
So easy to use that even a beginner can use it.

See this page in: English Espanol

This web site and all information written here is for information purposes only, WITHOUT ANY VARANTY. YOU ARE USING THIS PAGES ON YOU OWN RISK. You should always verify the accuracy of information provided on this page. We pay a big attention to provide you with the correct information. However, many spyware and malware programs use filenames of usual, non-malware processes and DLLs. If we have included information about winword.exe that is inaccurate, we would appreciate your help by getting us know about your user review. Also, web links to software and DLL vendors are provided just for your conform, and we cannot guarantee its accuracy nor relevance with DLL or process listed on this page. We are not affiliated with this pages. We are not responsible for misprints on this site or changes occured since this page was published. The product, software and operating system names mentioned on this web site, can be copyrighted and registered trademarks of their owners.