Temporary Word File in ..\INetCache\Content.Word are not trusted - is back

Question

Temporary Word File in ..\INetCache\Content.Word are not trusted - is back

Leon Pri-Mor 56

Problem- described here:
https://social.technet.microsoft.com/forums/lync/en-US/ca6af12f-26d9-42c1-acd9-28ef57c7f7c2/temporary-word-file-in-inetcachecontentword-are-not-trusted?forum=word

Is back, my client suddenly cannot open template that have macros.
Usually the macros are in Normal.dotm

Getting Error: ".\INetCache\Content.Word are not trusted"

Andreas Bergvall 1 Reputation point

2022-09-07T13:54:14.95+00:00

We have the same or very similar issue, first noticed some days ago. As part of an automated export- and conversion process, Word creates a .tmp file and then stops because the file is considered unsafe due to its location. We even tried setting the complete C drive as a trusted location in Word, but it didn't help.
bdharris26 1 Reputation point

2022-09-14T15:31:20.63+00:00

We are also running into this issue and similarly tried setting broad trusted locations for Word and Excel. The issue seemed to coincide with this change to security (https://learn.microsoft.com/en-us/deployoffice/security/internet-macros-blocked).
Mikel AA 80 Reputation points

2024-02-02T17:40:29.1666667+00:00
Hello, I am really desperate with this issue. Has anybody found a solution? I also have an excel document where I create a word document from it taking as a template another word.

@Ceasar Chen_MSFT

@Lauro Colasanti I've tried creating and opening the document (.Visible = True), but I always have the same problem. Any ideas?

Obviously I have those locations and the Excel at a trusted location.

Thanks!! This is my code:

Sub create_word_from_Template() Dim objWord as Object Dim path as String path = "C:\...\Word_template.docx" Set objWord = CreateObject("Word.Application") objWord.Documents.Add path, False, 0 ModifyWord objWord 'I just have this function to add text from the XLS objWord.ActiveDocument.SaveAs "C:\...\NewWord.docx" objword.Quit End Sub

4 answers

Your answer

Andreas Bergvall 1 Reputation point

2022-09-07T13:54:14.95+00:00

We have the same or very similar issue, first noticed some days ago. As part of an automated export- and conversion process, Word creates a .tmp file and then stops because the file is considered unsafe due to its location. We even tried setting the complete C drive as a trusted location in Word, but it didn't help.
bdharris26 1 Reputation point

2022-09-14T15:31:20.63+00:00

We are also running into this issue and similarly tried setting broad trusted locations for Word and Excel. The issue seemed to coincide with this change to security (https://learn.microsoft.com/en-us/deployoffice/security/internet-macros-blocked).
Mikel AA 80 Reputation points

2024-02-02T17:40:29.1666667+00:00

Hello, I am really desperate with this issue. Has anybody found a solution? I also have an excel document where I create a word document from it taking as a template another word.

@Ceasar Chen_MSFT

@Lauro Colasanti I've tried creating and opening the document (.Visible = True), but I always have the same problem. Any ideas?

Obviously I have those locations and the Excel at a trusted location.

Thanks!! This is my code:

Sub create_word_from_Template() Dim objWord as Object Dim path as String path = "C:\...\Word_template.docx" Set objWord = CreateObject("Word.Application") objWord.Documents.Add path, False, 0 ModifyWord objWord 'I just have this function to add text from the XLS objWord.ActiveDocument.SaveAs "C:\...\NewWord.docx" objword.Quit End Sub

Answer 1

Hi, @Leon Pri-Mor
Whether the location is added as a trusted location in Word, whether the dialog box allows all macros is checked.
Also, if you are installing a 64-bit version of Office, it is recommended to uninstall the 64-bit version to install the 32-bit version.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Leon Pri-Mor 56

Ceasar Hi.
Thank you for the answer.

All the macros enabled and the trusted location for templates set.

What I've discovered is that if you have a document that's not a template but do have macros, coping it from one directory to other fires this alarm.
Some of the documents with macros are in old "doc" format some "docx".

Setting trusted location to those libraries doesn't help. And it's not realistic do it-Many of my client have thousand's of folder and some times up to 15 logical drives.

Ceasar Chen_MSFT 4,481 Reputation points

2022-09-07T08:11:15.48+00:00

Do you mean to solve a large number of macro file trust problems?
Leon Pri-Mor 56 Reputation points

2022-09-15T11:51:41.96+00:00

It's getting worst.
Every day more and more clients , complaining about this problem.
If the word is closed this error is not firing up.
But if there is an open file and the user tries to open new document he's getting this error.
Christopher J. Edwards 1 Reputation point

2022-09-15T23:15:54.26+00:00

Do you have exclaimer running in any of the effected environments?
Ceasar Chen_MSFT 4,481 Reputation points

2022-09-19T06:02:49.627+00:00

You may need a script to add macro trust locations in bulk.
Leon Pri-Mor 56 Reputation points

2022-09-19T11:47:13.953+00:00
OK our developers found the problem.
Our software using word automation.

Set wordobj = GetObject(, "Word.Application") If Err.Number <> 0 Then WordWasOpen = False Set wordobj = CreateObject("Word.Application") Else WordWasOpen = True End If Err.Clear ' Clear Err object in case error occurred.

If for some reason GetObject(, "Word.Application") cant find word object and getting to CreateObject("Word.Application") and the word is open then this error fires up.

So with the new security it's impossible to use CreateObject("Word.Application") more then once.

For 20 years there was no problem using CreateObject("Word.Application") as many times as needed why does anyone need this change?
Ceasar Chen_MSFT 4,481 Reputation points

2022-09-20T02:30:55.65+00:00

Glad you can fix the problem, your approach will be helpful to users who have similar issues in the forum.
Paul Nagle 1 Reputation point

2022-10-03T08:21:28.723+00:00

Thanks for this information. Were your developers able to resolve this issue?
Leon Pri-Mor 56 Reputation points

2022-10-03T11:57:32.823+00:00

Paul Hi.

The solution is not to use early binding.

Error fired when using ===> Dim wordobj as New Word.Application

Late binding is the answer:
Set wordobj = GetObject(, "Word.Application")
Paul Nagle 1 Reputation point

2022-10-03T12:14:44.447+00:00

Thanks. Much appreciated,

Answer 3

Lauro Colasanti 121

I have a very similar problem but in a stranger situation.

The alarm notice is popping up only when I open a second file from an Access form with an OLE Linked Object Frame with a Word document. The first file is OK. Same trusted location.

Allowing all macros in trust center will not help!!!

immagine

Answer 4

Lauro Colasanti 121

Hi, some update.

If the Word files in the Ole BoundObjectFrame of Access are opened using the normal double click inside the control everything it's fine.

If the Word files are opened by the following simple VBA code, the first file opens correctly, the second one rises the security warnings.

The code:

sFileName = Me.txtFileName   
On Error Resume Next
Set objWordApp = GetObject("Word.Application")
If Err.Number <> 0 Then Set objWordApp = CreateObject("Word.Application")
On Error GoTo 0
With objWordApp   
.Visible = True   
.Activate   
.Documents.Open sFileName
End With 
Set objWordApp = Nothing

bdharris26 1 Reputation point

2023-11-27T19:32:34.4733333+00:00
We found something similar, but in Word documents being called by Excel VBA scripts. If there are no existing Word instances, something like the following works correctly, but doesn't otherwise:

Dim wordApp As Word.Application Set wordApp = New Word.Application Dim docCur As Word.Document Set docCur = wordApp.Documents.Open(...)

However, the issue seems related more specifically to the creation of new Word Application instances because a single script can open and use two+ documents in the same Application instance.

Share via

Temporary Word File in ..\INetCache\Content.Word are not trusted - is back

4 answers

Your answer