Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Following the release of Windows 10, I've decided to do a fresh install of the operating system rather than an inplace upgrade.
Everything is fine and works great, but for the Outlook client for CRM, which wont even install.
During the "Preparing..." phase, almost immediately a dialog box appears stating that "Microsoft Dynamics CRM has stopped working"
in event log I see :-
Log Name: ApplicationSource: Application ErrorDate: 02/08/2015 16:52:39Event ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: RWASUSDescription:Faulting application name: SetupClient.exe, version: 5.0.9690.1992, time stamp: 0x4f144247Faulting module name: MSVCR100.dll, version: 10.0.30319.1, time stamp: 0x4ba1dbbeException code: 0x40000015Fault offset: 0x0008d635Faulting process ID: 0x236cFaulting application start time: 0x01d0cd3b29fdd4e2Faulting application path: C:\Users\richard\crm\SetupClient.exeFaulting module path: C:\Users\richard\crm\MSVCR100.dllReport ID: 16c8dd7b-ecf4-4808-96b9-0d0e84e33a5eFaulting package full name: Faulting package-relative application ID:
The MSVCR100 file is there in the \crm\ folders, and I've manually installed the VC runtime libraries (all of them!) in an attempt to make it install, but so far no successes.
I've also tried this on another computer with win 10 and that does exactly the same thing.
Any ideas anyone?
Microsoft CRM 2015 (latest version) is not yet supported on Windows 10. I think the older version will not be support yet also. See this link for more details:
Same problem. Need help desperately !! Any solutions anyone?
I am also experiencing this. FYI - I did an upgrade installation over Windows 8.1 and it worked for nearly a week. This morning, the CRM client began crashing Outlook 2013. Re-installation would not complete on Windows 10.
Dynamics CRM 2011 won't ever be supported on Windows 10, as far as I know. You'll need to roll back to Windows 8.1 or plan to update to a newer version of CRM once support for Windows 10 is patched to CRM 2013 and 2015 in the next couple months.
The responses here are correct. Dynamics CRM 2011 will not be supported with Windows 10 at this time. The blog posted by Frank contains the relevant details:
It really should be able to run as a legacy program. Our 2013/15 upgrade plans are months away. Simply installing the client in compatibility mode should be able to work, but it does not.
Interestingly, it worked fine for several days (Wednesday until today) until I did an export to Excel, not it will not work at all. It also worked well on a previous Tech Preview build for me, which led us to believe that although it may not be "supported", it would "work".
So your response was CRM 2011 will not be supported for Windows 10 at this time. Does that mean Microsoft is still considering patching it so at least the outlook plugin works?
we can't be the only company in the world using CRM2011, and not particularly wanting to upgrade for no reason, other than to support the latest OS. What is the point of supporting a client OS for 10 years if the products that run upon it expire after 4 ?! There must be some way of allowing this plugin to work even if there isn't full on support.
Support for 2011 has not yet been confirmed. As of this time, no released version of CRM is supported with Windows 10 until the updates have released that are mentioned in the blog. Please keep an eye on that support blog for any changes.
We've been testing Windows 10 in a lab environment for several months and finally rolled it out to a small group of volunteers in our environment. This exact issue cropped up for us.
We have one user who had the CRM 2011 for Outlook client installed on Windows 7, then upgraded to 10. He claims that this is still working for him, but as he is not on-site I haven't been able to confirm at this time.
Sincerely hoping that this is patched in the near future.
I can confirm that the client works when you upgrade from Windows 8.1 in Outlook 2013. When I initially did the upgrade, everything worked well until I exported a view to Excel. This caused an Outlook crash and from then on, Outlook would not open with the client enabled. I also could not reinstall the client - with the errors mentioned here.
I ended up doing a clean installation of Windows 10 to test. The client would not install.
Then, I clean installed Windows 8.1, Outlook 2013, and the CRM Client only, then upgraded to Windows 10 and finished restoring my machine. Since then (over a week), my machine has worked fine.
I will, from now on, use the browser client for anything other that routine work. (exports), since I do not want to go through a restore process.
I have created an image of my machine in this state, just in case.
This blog has now been updated: community.dynamics.com/.../dynamics-crm-support-with-windows-10-edge-browser-and-office-2016
Looks like we may not need to panic too much then :)
windows 8 install then upgrade in the short term, until the next rollup is released.the questions are -when will it be released? - what rollup number will this fix be in- will we be able to download a fully up-to-date client rather than the current old version which then needs the rollup applying after the initial install.
CRM not installing on a clean OS really created a big problem in our Windows 10 pilot program so I dug in and created a workaround that will allow CRM 2011 Outlook client to be installed on a fresh install of Windows 10. Seem like after looking at the log files that the install was crashing when invoking Windows Update and since WU is different in Win10 it cant recover. So I tore apart the log file of a clean install on a Windows 7 computer and then recreated it on my Win10 test. In do so this stripes off the "SetupClient.exe" wrapper that's making the WU call. I've automated the process using MDT and SCCM but here are the basic steps to follow on a Win10 x64 OS. x86 obviously will require the proper x86 installs.
Some of the installs are running silent so they do not give you GUI confirmation that the install completed successful, check the logs if in doubt.
Likes others here, we've been testing Win10 with CRM 2011 via OS upgrade and had no problems. So far with this install method everything seems to work. Interested to hear if others have an issue with CRM AFTER the install.
Hope this helps with testing until the official update comes out. Ken
Thanks GeoTech :) - Your fix works like a charm :) I skipped 4.1 and 4.2(SQL EXPRESS) as I don't need it off line, and success - CRM in Outlook :) - thanks so very much - and to the other folk reading, just follow his Geotech's guidance above.
I was able to get Dynamics CRM 2011 working with Windows 10. I had to download and install IE 11 manually and make it my default browser. Once I did that and rebooted the CRM Outlook toolbar came back on and works fine. As a side not this also fixes the Cognos 8 report studio that will not work in Edge.
Thank you so so much for posting this. Step 3 (client.msi), skipping SetupClient.exe and its pre-requisite downloads that no longer work saved me.
Business Applications communities