DisplayFusion RSS: Office 365 and displayFusion https://www.displayfusion.com/Discussions/RSS/?TopicID=288a8da5-cd04-4593-b755-62b183135e7a DisplayFusion RSS: Office 365 and displayFusion Sat, 23 May 2026 05:52:45 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=288a8da5-cd04-4593-b755-62b183135e7a RE: Office 365 and displayFusion https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#4 Fri, 01 Aug 2014 16:14:10 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#4 DisplayFusion Ok, could you try creating a rule on the Settings > Compatibility tab for C:\Program Files\Microsoft Office 15\ClientX86\OfficeClickToRun.exe, and in the rule, enable the "Disable Application Hooks" option? After creating the rule, restart DisplayFusion, then try launching Office 365 again.

Please let me know how that works out and we'll go from there.

Thanks! ]]> RE: Office 365 and displayFusion https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#3 Thu, 31 Jul 2014 19:29:50 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#3 DisplayFusion No error message, just would say an error occurred.

Checking the event viewer and got a couple:

Code
Copy
Select All

Could not load OSD file \\focwds01\content\DWGSEE_MNT\DWGSee Pro 3.4.6.6.osd


Code
Copy
Select All

Faulting application name: OfficeClickToRun.exe, version: 15.0.4631.1001, time stamp: 0x53a28e77
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f0c22
Exception code: 0x40000015
Fault offset: 0x0008d6fd
Faulting process id: 0xd64
Faulting application start time: 0x01cfaccadbe8b4b2
Faulting application path: C:\Program Files\Microsoft Office 15\ClientX86\OfficeClickToRun.exe
Faulting module path: C:\Program Files\Microsoft Office 15\ClientX86\MSVCR100.dll
Report Id: 1a393052-18be-11e4-a3a4-18a9052f4c5c


Code
Copy
Select All

Fault bucket 360808408, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OfficeClickToRun.exe
P2: 15.0.4631.1001
P3: 53a28e77
P4: MSVCR100.dll
P5: 10.0.40219.1
P6: 4d5f0c22
P7: 40000015
P8: 0008d6fd
P9: 
P10: 

Attached files:
C:\Users\maneumann\AppData\Local\Temp\WERB8D4.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\maneumann\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_OfficeClickToRun_e12242afcd54c8bb1a6e65d568ef3433715b75_0588d0c6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1a393052-18be-11e4-a3a4-18a9052f4c5c
Report Status: 0


Those are a few, either errors or warnings ]]> RE: Office 365 and displayFusion https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#2 Thu, 31 Jul 2014 19:02:28 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a#2 DisplayFusion That's strange indeed! Do you get any errors when you try to launch Office 365? ]]> Office 365 and displayFusion https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a Thu, 31 Jul 2014 14:31:26 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/office-365-and-displayfusion/?ID=288a8da5-cd04-4593-b755-62b183135e7a DisplayFusion Hello;

I was hoping to pick your brains again - as last time you were invaluable in helping me! :laugh:

I installed displayfusion on my work computer yesterday, along with Mosaico (amazing combo btw) with Office 365 installed. All day yesterday it was fine.

This morning when I turned on my machine it all opened up, but Office 365 would not launch what so ever. I found that very strange.

As soon as I closed displayfusion, it opened all with no issue.

Then I can open up display fusion again! So a workaround exists

Any idea of a debug setting to change?

Running x86 Windows 7 SP1 Enterprise

EDIT: One change I made before outputting the log was disabling launch with Windows startup. Previously was enabled ]]>