Maybe. I worry about what's insinuated here, but we can try it: https://gist.github.com/cowlibob/717446



The fixes in Ruby call OleInitialize and OleUninitialize per thread.

```
    git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@38869 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

commit 27ed294c7134c0de582007af3c915a635a6506cd
Author: nobu <nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
Date:   Fri Jan 18 02:24:35 2013 +0000

    win32ole: OLE uninitialize

    * ext/win32ole/win32ole.c (ole_initialize): uninitialize OLE at thread
      ends.  [Bug #2618] [ruby-core:27634]


    git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@38868 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

commit 588504b20f5cc880ad51827b93e571e32446e5db
Author: nobu <nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
Date:   Fri Jan 18 02:23:37 2013 +0000

    win32ole: OLE initialize per threads

    * ext/win32ole/win32ole.c (ole_initialize): initialize OLE for each
      threads.  [Bug #2618] [ruby-core:27634]
```