On Windows 10 build 10162 after installing Office 2016 Skype for Business started throwing the error: The operating system is not presently configured to run this application.
Using Task Manager I right clicked lync.exe and created a dump file.
Opening in WinDbg using ~k I found the thread 4 was displaying the dialog box, and set the context to that thread using ~4s
As the dmp file was 32-bit process captured with 64-bit task manager I set to 32 bit context
.load wow64exts
!wow64exts.sw
Looking at the stack:
0:004:x86> kv
# ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
00 0503c928 75adbed2 00000000 00000000 00000000 user32!WaitMessage+0xc
01 0503c958 75b2e6a6 00000000 75b2c560 0503cba0 user32!GetCapture+0x122
02 0503ca24 75b2d58a 0503cba0 1a0bcf90 00000000 user32!SoftModalMessageBox+0xea6
03 0503cb88 75b2d2ac 1a0bcf90 00000000 00000000 user32!MessageBoxW+0x2ba
04 0503cc08 75b2d20b 00000000 1a0bcf90 00000000 user32!MessageBoxTimeoutW+0x6c
05 0503cc3c 75b2cfeb 00000000 1a07d200 00000000 user32!MessageBoxTimeoutA+0x7b
06 0503cc5c 75b2cfb8 00000000 1a07d200 00000000 user32!MessageBoxExA+0x1b
07 0503cc78 559ca7b6 00000000 1a07d200 00000000 user32!MessageBoxA+0x18
08 0503cc98 557c3fcd 0503ccb4 55685c96 00000001 OLMAPI32_55680000!Validate_SetValidationFlags+0x79a0
09 0503cca0 55685c96 00000001 55a99db0 55aaab94 OLMAPI32_55680000!ShutdownEDPSessionProtector+0x5ebe4
0a 0503ccb4 55685c66 00000001 0503cd0c 00000000 OLMAPI32_55680000!ReadRegDWordValueAndPolicy+0x45d
0b 0503cccc 55685cbb 55a1ecd0 00000001 0503cd0c OLMAPI32_55680000!ReadRegDWordValueAndPolicy+0x42d
0c 0503cce8 556848b4 00000001 0503cd0c 00000001 OLMAPI32_55680000!ReadRegDWordValueAndPolicy+0x482
0d 0503cd3c 55685c4d 55a99a7c 55aa18e4 00000000 OLMAPI32_55680000!FIsMsoAuthEnabled+0x325a
0e 0503cd80 556853d7 55680000 00000001 00000000 OLMAPI32_55680000!ReadRegDWordValueAndPolicy+0x414
0f 0503cda4 55681143 55680000 00000001 00000000 OLMAPI32_55680000!FIsMsoAuthEnabled+0x3d7d
10 0503cde4 55681017 55680000 00000001 00000000 OLMAPI32_55680000+0x1143
11 0503cdf8 77d88b4e 55680000 00000001 00000000 OLMAPI32_55680000+0x1017
12 0503ce18 77d5652b 55681000 55680000 00000001 ntdll_77d20000!RtlQueryUnbiasedInterruptTime+0x33e
13 0503ce68 77d5432f 00000001 00000000 e5ee6e3b ntdll_77d20000!LdrShutdownThread+0x29b
14 0503cee8 77d54128 1a0b05b8 00000000 0503cfa4 ntdll_77d20000!LdrGetDllHandleByName+0x56f
15 0503cf0c 77d53949 0503cf27 0503cfa8 0503cfa4 ntdll_77d20000!LdrGetDllHandleByName+0x368
16 0503cf28 77d55b30 e5ee6fa3 0503d0e8 0503d178 ntdll_77d20000!LdrShutdownProcess+0x949
17 0503cf70 77d65ec4 00000600 00000004 00000000 ntdll_77d20000!RtlCreateUnicodeStringFromAsciiz+0x6f0
18 0503d0bc 77d68475 00000000 00000001 0503d0e0 ntdll_77d20000!ApiSetQueryApiSetPresence+0x124
19 0503d140 76834248 00000009 0503d168 0503d178 ntdll_77d20000!LdrLoadDll+0x75
1a 0503d180 75e60a3c 0503d228 00000000 00000008 KERNELBASE!LoadLibraryExW+0x138
1b 0503d1a4 75e609b7 00000008 0503d1f8 0503d228 combase!GetHGlobalFromStream+0x55c
1c 0503d1c8 75e607db 0503d1f4 0503d1f0 0503d1f8 combase!GetHGlobalFromStream+0x4d7
1d 0503d204 75e62b6d 0503d224 75f85208 80004005 combase!GetHGlobalFromStream+0x2fb
1e 0503d454 75eaff4f 00000001 0503d7cc 0503d4bc combase!CLSIDFromString+0x110d
1f 0503d784 75e64d22 0503d7ac e25cfd03 0503d7b8 combase!CoCreateInstance+0x1ecf
20 0503d7b8 75e64f6c 0503de74 75e64e40 00000000 combase!RoActivateInstance+0xc32
21 0503d828 75e684fa 75f85c34 00000000 0503de74 combase!RoActivateInstance+0xe7c
22 0503d874 75e65522 0503de74 00000000 0503e510 combase!RoActivateInstance+0x440a
23 0503d8cc 75e658e5 75f85c38 00000000 0503de74 combase!RoActivateInstance+0x1432
24 0503d8fc 75e65860 75f85c30 00000001 00000000 combase!RoActivateInstance+0x17f5
25 0503d920 75e65b5b 75f85c30 0503dca0 00000000 combase!RoActivateInstance+0x1770
26 0503d960 75e659d7 75f85c30 0503dca0 00000000 combase!RoActivateInstance+0x1a6b
27 0503d990 75e684db 75f85c30 00000000 0503de74 combase!RoActivateInstance+0x18e7
28 0503d9dc 75e667fd 0503de74 00000000 0503e510 combase!RoActivateInstance+0x43eb
29 0503dc40 75e684e2 75f85c2c 00000000 0503de74 combase!RoActivateInstance+0x270d
2a 0503dc8c 75ead106 0503de74 00000000 0503e510 combase!RoActivateInstance+0x43f2
2b 0503e608 75eac379 00000003 00000000 00000001 combase!RoGetActivationFactory+0x68b6
2c 0503e650 75eae1b2 00000003 00000000 00000001 combase!RoGetActivationFactory+0x5b29
2d 0503e688 604edfbd 605770f8 00000000 00000003 combase!CoCreateInstance+0x132
2e 0503e710 605159c4 605770f8 00000000 00000003 OLMAPI32!HrGetCrawlScopeManagerWrapper+0x26aa
2f 0503e738 60515958 1154cfb0 0503e774 00000001 OLMAPI32!HrGetAcctManagerFromSession+0x35
30 0503e75c 56e4beb6 113c8440 0503e774 0503ee88 OLMAPI32!HrGetAcctManager+0x62
31 0503e778 56e4b817 1a0b4f60 00000104 114139b8 MSPST32!OSTServiceEntry+0x32d69
32 0503edac 56e12f1c 114139b8 1a0bc1d8 00000000 MSPST32!OSTServiceEntry+0x326ca
33 0503f2e8 56fcf503 114139b8 113c8440 00000000 MSPST32!MSProviderInit+0xc8b
34 0503f3bc 56fc3feb 113e6388 1a0b2290 113c8440 EMSMDB32!MSProviderInit+0x14445
35 0503f560 56fc3975 113e6388 113c8440 00000000 EMSMDB32!MSProviderInit+0x8f2d
36 0503f5a0 604eb519 113e6388 113c8440 00000000 EMSMDB32!MSProviderInit+0x88b7
37 0503f5e0 604eb2a0 0503f71c 114c71a8 9000009c OLMAPI32!HrCreateConnectionManager+0x47d7
38 0503f634 604eb111 00000000 114e9240 0503f6c0 OLMAPI32!HrCreateConnectionManager+0x455e
39 0503f674 604e9dac 0503f71c 0503f6c0 63bf1bf4 OLMAPI32!HrCreateConnectionManager+0x43cf
3a 0503f700 604e95be 0503f71c afaaf001 114e9150 OLMAPI32!HrCreateConnectionManager+0x306a
3b 0503f7a4 604e951d 1154cfb0 00000000 00000082 OLMAPI32!HrCreateConnectionManager+0x287c
3c 0503f7ec 639ea99a 1154cfb0 00000000 00000082 OLMAPI32!HrCreateConnectionManager+0x27db
3d 0503f860 639e9e32 0503f8a0 00000000 0503f8b4 MSO!Ordinal2928+0x2676
3e 0503f870 639f7508 0503f8a0 afa3272b 114c6ba8 MSO!Ordinal2928+0x1b0e
3f 0503f8b4 639f74a7 1123b590 00000000 0503f900 MSO!Ordinal7732+0x21c1
40 0503f8f0 639c3747 00000000 00995f08 00000000 MSO!Ordinal7732+0x2160
41 0503f934 639c3611 11547048 00995f08 0503f95c MSO!Ordinal2317+0x7e7
42 0503f944 639c357d 11547050 114dd598 11547050 MSO!Ordinal2317+0x6b1
43 0503f95c 636fbc0d 11547050 114dd598 636ecb7f MSO!Ordinal2317+0x61d
44 0503f98c 636ebab1 0503f9fc 0503f9e0 00950af8 MSO!Ordinal1788+0x4c3
45 0503f9a4 636e9422 0503f9fc 636e8690 00950af8 MSO!Ordinal1978+0xfc
46 0503f9d8 636e86e9 00000000 636e86e9 0503f9fc MSO!Ordinal1981+0x1cdd
47 0503fa2c 75703774 00950af8 75703750 f0a53cda MSO!Ordinal1981+0xfa4
48 0503fa40 77d790d1 00950af8 e5ee5a5b 00000000 kernel32!BaseThreadInitThunk+0x24
49 0503fa88 77d7909c ffffffff 77d9d77f 00000000 ntdll_77d20000!RtlWalkFrameChain+0x141
4a 0503fa98 00000000 636e8690 00950af8 00000000 ntdll_77d20000!RtlWalkFrameChain+0x10c
0:004:x86> da 1a07d200
1a07d200 “The operating system is not pres”
1a07d220 “ently configured to run this app”
1a07d240 “lication…”
0:004:x86> du 0503d228
0503d228 “C:\Program Files (x86)\Microsoft”
0503d268 ” Office\root\Office16\OLMAPI32.D”
0503d2a8 “LL”
0:004:x86> lmvm olmapi32
Browse full module list
start end module name
604c0000 608a4000 OLMAPI32 (export symbols) OLMAPI32.DLL
Loaded symbol image file: OLMAPI32.DLL
Image path: C:\Program Files (x86)\Microsoft Office\Office15\OLMAPI32.DLL
Image name: OLMAPI32.DLL
Browse all global symbols functions data
Timestamp: Wed May 13 01:23:36 2015 (55521AF8)
CheckSum: 003F08B5
ImageSize: 003E4000
File version: 15.0.4727.1000
Product version: 15.0.4727.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 0.0 Unknown
File date: 00000000.00000000
Translations: 0000.04e4
CompanyName: Microsoft Corporation
ProductName: MAPI32
InternalName: MAPI32.DLL
OriginalFilename: MAPI32.DLL
ProductVersion: 15.0.4727.1000
FileVersion: 15.0.4727.1000
FileDescription: Extended MAPI 1.0 for Windows NT
0:004:x86> lmvm lync
Browse full module list
start end module name
00ee0000 025d8000 lync (export symbols) lync.exe
Loaded symbol image file: lync.exe
Image path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Image name: lync.exe
Browse all global symbols functions data
Timestamp: Tue May 19 19:02:46 2015 (555AFC36)
CheckSum: 01702E87
ImageSize: 016F8000
File version: 15.0.4727.1001
Product version: 15.0.4727.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0000.04e4
CompanyName: Microsoft Corporation
ProductName: Microsoft Office 2013
InternalName: Lync
OriginalFilename: Lync.exe
ProductVersion: 15.0.4727.1001
FileVersion: 15.0.4727.1001
FileDescription: Skype for Business
0:004:x86> lmvm OLMAPI32_55680000
Browse full module list
start end module name
55680000 55b0b000 OLMAPI32_55680000 (export symbols) OLMAPI32.DLL
Loaded symbol image file: OLMAPI32.DLL
Image path: C:\Program Files (x86)\Microsoft Office\root\Office16\OLMAPI32.DLL
Image name: OLMAPI32.DLL
Browse all global symbols functions data
Timestamp: Sat Jul 04 21:31:40 2015 (5597C41C)
CheckSum: 004853C4
ImageSize: 0048B000
File version: 16.0.4229.1002
Product version: 16.0.4229.0
File flags: 22 (Mask 3F) Pre-release Special
File OS: 40004 NT Win32
File type: 0.0 Unknown
File date: 00000000.00000000
Translations: 0000.04e4
CompanyName: Microsoft Corporation
ProductName: MAPI32
InternalName: MAPI32.DLL
OriginalFilename: MAPI32.DLL
ProductVersion: 16.0.4229.1002
FileVersion: 16.0.4229.1002
FileDescription: Extended MAPI 1.0 for Windows NT
So in the stack trace we have two different versions of OLMAPI32.dll – v15 pre-release v16.
We can easily see it gets loaded when using ProcMon and filtering Details Contains OLMAPI32.dll from this registry key:
However if Skype For Business 2015 and Outlook 2016 are closed, and opened in the following order,Skype launches correctly.
1) Outlook 2016
2) Skype For Business 2015
In this scenario only the v15 version of DLL gets loaded:
After several launches of Outlook 2016 & Lync, the problem went away.
chentiangemalc 
It saddens me to say that Skype has become notoriously unreliable/unstable since Microsoft took the reins. As someone who relies heavily upon it, I appreciate the fact that it comes at no charge but live in hope that one day it will stabilize!
Very in depth analysis with this issue. Can I exclude a DLL loading or will Skype for Business not load at all?
Thank you for taking the time to figure this out. It is frustrating that, a year and a half later, it is still on ongoing problem which Microsoft does not care to fix. I’m trying your solution, opening the two programs in the prescribed order, and hope it does work.
Still getting this. In my Skype4B client – which is set to start automatically (but Outlook isn’t) – I (and many other users) are getting this error now. I couldn’t get into recording manager either, it would error. Some users report that accessing voice mails through the Skype4B client is unreliable as well.
I tested the steps here by closing Skype4B manually, closing outlook. Loading Outlook, then Skype and could get into recording manager. Next time someone reports a voice mail problem we’ll try that also and see if these steps fix it.
Obviously the solution here isn’t a full rebuild of the workstations affected. Myself, I’ve only been seeing this for a few weeks so it’s obviously a bug with some Office 365 (using C2R) update recently.
go to here: https://www.catalog.update….
and download the update from 10/9/2018 for either x86 or x64 respectively
Has resolved the issue for virtual machines today