We highly recommend backing up the registry before you modify it. Therefore, please ensure that you follow these steps carefully. However, serious problems might occur if you modify the registry incorrectly. The resolution requires you to modify the registry. This behaviour breaks the experience for both existing profiles, and newly created profiles - fortunately we have discovered a workaround involving a registry fix, for which the steps will be detailed below. Outlook prompts the user to log in, but logging in will fail as it's effectively requesting credentials to authenticate against the O365 service, rather than Hosted Exchange credentials. This causes problems for customers who aren't using O365 for their mail service (our Hosted Exchange customers), especially if the user has an unused mailbox within the O365 service, or if the the user has a personal O365 subscription using their business email address.
Outlook 2016 crashes on startup during autodiscover update#
When I look at the references with DotPeek it says it takes this one: C:\Program Files (x86)\Microsoft XNA\XNA Game Studio\v4.0\References\Windows\x86\ (which exists).A recent update by Microsoft to the Outlook 2016 Click2Run version has introduced a functionality change whereby Outlook is prioritising Office 365 for the autodiscover queries above all other autodiscover methods.
What more can I do to try to fix this issue? I will reinstall my system in two months from now, which might help, but I think it is too radical to do it now for the sake of 1 program that refuses to launch. I decompiled the exe to look at its references, which are:Īll these dll's were succesfully resolved. placing the following (missing) dll's in the system32/syswow64/game directory.Complete removal of all System32/d2*.dll and d3*.dll and reinstalling directx (Which broke a few other games).Installing on game on C drive instead of F drive.dism /Online /Cleanup-Image /RestoreHealth.Completely removed XNA 4.0 and reinstall.Here is what I tried (with reboots in between): She only got a few more dll's available (which I copied afterwards, but didn't help).
My wife also has the game and it works on her machine, however Dependency Walker reported no big differences. One of the strange things is that the game exe is x86 and all loaded dll's are 圆4. I used Dependency Walker to inform me about missing dll's or incompatible versions. I like to fix my own problems, but after 6 hours I give up.
Report Id: b8cdbcca-597d-4eb4-a44c-47f2b8c510a5įaulting package-relative application ID:įollowed by: Fault bucket 108078241334, type 1 30711, time stamp: 0x5705b1efįaulting module name: KERNELBASE.dll, version: 6.162, time stamp: 0x56cd55abįaulting application start time: 0x01d19eee1ec0b80dįaulting application path: F:\Steam\steamapps\common\Stardew Valley\Stardew Valley.exeįaulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Right after that: Faulting application name: Stardew Valley.exe, version. To me this sounds like a bad dll or a wrong architecture for a dll, but I haven't been able to sort out what the problem is. When I took a look in the eventviewer I saw the following information: Application: Stardew Valley.exe Framework Version: v9ĭescription: The process was terminated due to an unhandled exception.Įxception Info: System.BadImageFormatException at I bought the game Stardew Valley on steam, installed it, launched it.