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

msdtc.exe: msdtc missing on Windows Embbeded 8 Standars WE8S

I have just installed my first ever WE8S
I have used the image builder wizard and the Target Analyzer probe.

After install of WE8S I have tried to install MS SqlServer 2012 express, but it fails saying that it cant find a registry setting for msdtc.
That is true. msdtc is not mentioned anywhere in the registry.
msdtc.exe is not found in C:windowssystem32

What should I do in order to have msdtc installed?

smss.exe: Can't list all process on windows 7 64 bit

I programmed an application that allows listing the processes running on the machine, my OS is Windows 7 64 bit. When I debug, all processes are listed, however after build out, on the x64 and x86 platform, missing some process as smss.exe, svchost.exe, csrss.exe ... Can you help me? Thank you ...

winamp.exe: how to debug a dll winamp plugin in Visual Studio 2010 written in C++?

I'm developing a Winamp plugin. I have a project that builds a .dll file. This file is actually the plugin. I want to debug that plugin.
I need some recipe Step by step. I have already set the Configuration Properties - > Debug ging -> Command to 'C:Program Files (x86)Winampwinamp.exe'. So, when I hit debug winamp actually starts the plugin but then some C++ runtime fatal error occure.


The question is how to prepare for the debugging? How to tell winamp.exe

frameworkservice.exe: Connecting to WMI: 0x800706ba errors on some machines (but not all)

When I try to connect to WMI from Powershell, ConfigMgr, or WMI explorer, I can talk to the majority of my computers, but some (maybe 30%?) return an 0x800706ba (RPC server is unavailable).

If I turn the firewall off on the remote machine, the queries start working. I have tried a bunch of different configurations of firewall settings, though, and I can't seem to figure out what the right combination of exceptions is.

Here's the relevant bits of my firewall config on the remote ma

monitor.exe: Hiding the Process Monitor application window

I am creating a scheduled task to run process monitor at its highest privileges. I have a windows service that executes the scheduled task on start. Thus on start of my service, process monitor.exe will be executed shown in a window. But I don't want to see the window. I just want the process monitor.exe to run in the background without displaying any windows.

In AutoIT, there is a command: Run (Procmon.exe,'',@SW_Hide) @SW_Hide = Hidden Window

I tried this:

foreach (Process

kernel32.dll: how to get Processor ID using Kernel32.dll

I want to know if there is an Entry point for kernel32.dll , that is related to any processor data (ID , Serial , etc ... )
and I tried to Google it but I didn't find good results .

Note: I already know WMI , but I need something related to Kernel !

javaw.exe: javaw.exe crashes on creating JFrame

I'm using eclipse on a windows 7 x64 to create a new Java Application.

This is my code:

import java.awt.EventQueue;

public id Testen {

private JFrame frame;

* Launch the application.
public static void main(String[] args) {
EventQueue.invokeLater(new Runnable() {
public void run() {
try {
Testen window = new Testen();

msdtc.exe: When machine-wide tracing is enabled, where does ODBC store logs for NETWORKSERVICE?

When I enable machine-wide tracing in odbcad32.exe, it says:

A log file will be created if none exists for every user identity under which a process using odbc is running.

However, it doesn't say where they'll be created. Presumably for normal users they'll be under %LOCALAPPDATA%, since that's the default path, but what about system users like NETWORKSERVICE, which the MS Distributed Transaction Services (msdtc.exe)?

It's using ODBC - I have a debugger attached to

dllhost.exe: How to launch COM server in separate dllhost process?

My COM component implemented as surrogated dll. I create one by calling CoCreateInstanceEx(), but it started in shared dllhost.exe process. Is there a way to launch my COM component in separate dllhost process?

ntvdm.exe: Create a 16bit application?

I want to create a 16 bit Dos application and want it to run using the NTVDM.exe on my 32bit windows 7 machine. How do I do it?
I basically want my application to do the file operations through the NTVDM and for that I think I'll need a 16 bit application first, Is there any other way?

I don't need an Emulator, I need to create an 16-bit app

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.