Not sure if this is the right forum?

Getting this error (copied from Event Viewer) on a Windows 8.1 Pro client - an event ID of 1000, every time at the start of profile creation when logging in with a domain account. So explorer.exe crashes because of "twinui.appcore.dll" and profile creation is taking a very long time (about 17 minutes).

Then after being stuck during "Almost ready" screen we are getting a Start-button that is stuck (non-clickable) (and also arrows on the metro-screen icons). Restarting explorer.exe manually helps to get a functional Start-button again.

Tried using a roaming profile and without using a roaming profile (Group Policy setting to always keep profiles local). That does not seem to matter.

Naam van toepassing met fout: Explorer.EXE, versie: 6.3.9600.17667, tijdstempel: 0x54c6f7c2

Naam van module met fout: twinui.appcore.dll, versie: 6.3.9600.17415, tijdstempel: 0x54503801
Uitzonderingscode: 0x80270233
Foutmarge: 0x000000000008cb57
Id van proces met fout: 0xf28
Starttijd van toepassing met fout: 0x01d05bf587567d80
Pad naar toepassing met fout: C:\Windows\Explorer.EXE
Pad naar module met fout: C:\Windows\System32\twinui.appcore.dll
Rapport-id: cf9c3ec8-c7e8-11e4-8262-0019bbd6f620
Volledige pakketnaam met fout: 
Relatieve toepassings-id van pakket met fout: 

Using Samba 3.6.25 with an LDAP back-end. Installed all updates for Windows 8.1 Pro client.

Thanks in advance for any advice.

Hi Wieger,

"every time at the start of profile creation when logging in with a domain account. "

Do you mean the issue only occur with this specific account ? Have you installed any third party software in the machines before this issue ?

Please try to perform a cleanboot to verify whether it is caused by a third party software .
How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135

We can run "sfc /scannow "or "dism /online /cleanup-image /restorehealth " to check the health of the system .

Best regards

Hello MeipoXu,

Thanks for your response.

No, not for a specific account. I've tried multiple domain accounts. The accounts do authenticate, it's just explorer.exe that is crashing at time of login (when profile is created).

It occurs even when I use a clean install of the 90-day trial version of Windows 8.1 (Enterprise). Without updates and with all updates it occurs. Also, without any third-party software (no anti-virus software installed).

To be fair though: I do have it working using using my home network in a virtual machine.

Earlier on I had Samba 3.6.24 installed in my home network and it did not work either (explorer.exe crashed also). But installing Samba 3.6.25 (latest version) apparently made it go away using my home network.

Or it coincided with that update?

Installing that latest version in my (voluntary, non-profit) work environment did not make it go away.

I'll try and gather some more information (like a crash dump).

Pasting the crash dump analysis using WinDbg (x64):

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\LocalDumps\explorer.exe.824.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
Built by: 6.3.9600.17031 (winblue_gdr.140221-1952)
Machine Name:
Debug session time: Thu Mar 12 11:53:12.000 2015 (UTC + 1:00)
System Uptime: 0 days 21:10:37.682
Process Uptime: 0 days 0:01:05.000
................................................................
....................................
Loading unloaded module list
...........
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(338.f94): Unknown exception - code 80270233 (first/second chance not available)
kernel32!RaiseFailFastException+0xae:
00007ffe`cb2faabe e8b1000000      call    kernel32!SignalStartWerSvc (00007ffe`cb2fab74)
0:018> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for sppc.dll -

FAULTING_IP:
twinui_appcore!CCriticalFailureHandler::_RaiseFailFastException+c7
00007ffe`bed7cb57 488b4d37        mov     rcx,qword ptr [rbp+37h]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ffebed7cb57 (twinui_appcore!CCriticalFailureHandler::_RaiseFailFastException+0x00000000000000c7)
   ExceptionCode: 80270233
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: ffffffff80070005

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
rax=000000000a14f560 rbx=000000000a14fa70 rcx=000000000a14f560
rdx=0000000000000000 rsi=0000000000000001 rdi=000000000a14f560
rip=00007ffecb2faabe rsp=000000000a14f480 rbp=000000000a14fad9
 r8=0000000000000000  r9=0000000000000006 r10=0000000000000000
r11=00007ffecb544dd7 r12=00007ffebed00090 r13=0000000008234160
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000244
kernel32!RaiseFailFastException+0xae:
00007ffe`cb2faabe e8b1000000      call    kernel32!SignalStartWerSvc (00007ffe`cb2fab74)

PROCESS_NAME:  explorer.exe

ERROR_CODE: (NTSTATUS) 0x80270233 - <Unable to get error code text>

EXCEPTION_CODE: (HRESULT) 0x80270233 (2150040115) - <Unable to get error code text>

EXCEPTION_PARAMETER1:  ffffffff80070005

NTGLOBALFLAG:  2000100

APPLICATION_VERIFIER_FLAGS:  48004

APP:  explorer.exe

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

FAULTING_THREAD:  0000000000000f94

BUGCHECK_STR:  APPLICATION_FAULT_SHELL_COMPONENT_STARTUP_FAILURE_ERROR_CODE_ffffffff80270233

PRIMARY_PROBLEM_CLASS:  SHELL_COMPONENT_STARTUP_FAILURE_ERROR_CODE_ffffffff80270233

DEFAULT_BUCKET_ID:  SHELL_COMPONENT_STARTUP_FAILURE_ERROR_CODE_ffffffff80270233

LAST_CONTROL_TRANSFER:  from 00007ffebed7cb57 to 00007ffecb2faabe

STACK_TEXT:  
00000000`0a14f480 00007ffe`bed7cb57 : 00000000`80070005 00000000`00000004 ffffffff`80070005 00000000`00000000 : kernel32!RaiseFailFastException+0xae
00000000`0a14fa50 00007ffe`bed7c8c2 : 00000000`00000a9c 00000000`0a14fc20 00000000`000003a8 00000000`000003a8 : twinui_appcore!CCriticalFailureHandler::_RaiseFailFastException+0xc7
00000000`0a14fb40 00007ffe`bed8b349 : 00000000`00000000 00007ffe`bed00090 00000000`000003a8 00000000`00000004 : twinui_appcore!CCriticalFailureHandler::HandleFailure+0xba
00000000`0a14fb90 00007ffe`bed19d8b : 00000000`08242340 00000000`0a14fc00 00000000`00000000 00007ffe`bed34838 : twinui_appcore!`Microsoft::WRL::Module<1,Microsoft::WRL::Details::DefaultModule<1> >::Create'::`2'::`dynamic atexit destructor for 'module''+0x7a79
00000000`0a14fbd0 00007ffe`c5055bf1 : 00000000`80070005 00000000`08242340 00000000`00000000 00007ffe`bed19d30 : twinui_appcore!CProcessLifetimeManager::PerformDelayedInitialization+0x5b
00000000`0a14fc20 00007ffe`c5055519 : 00000000`00000000 00000000`08242340 00000000`00000000 00000000`00000034 : windows_immersiveshell_serviceprovider!CImmersiveShellController::_CreateComponents+0x536
00000000`0a14fcc0 00007ffe`c505566e : 00007ffe`00000045 00000000`00000000 00000000`082335f8 00000000`02ea60e8 : windows_immersiveshell_serviceprovider!CImmersiveShellController::_ImmersiveShellComponentsThreadProcInternal+0x17d
00000000`0a14fd50 00007ffe`b41995cd : 00007ffe`c5050000 00007ffe`c50555f0 00000000`00000000 00000000`00000000 : windows_immersiveshell_serviceprovider!CImmersiveShellController::s_ImmersiveShellComponentsThreadProc+0x7a
00000000`0a14fd80 00007ffe`cb2113d2 : 00007ffe`b4199580 00000000`00000000 00000000`00000000 00000000`00000000 : verifier!AVrfpStandardThreadFunction+0x4d
00000000`0a14fdc0 00007ffe`cb51e954 : 00007ffe`cb2113b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22
00000000`0a14fdf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34


FOLLOWUP_IP:
twinui_appcore!CCriticalFailureHandler::HandleFailure+ba
00007ffe`bed7c8c2 488b6c2458      mov     rbp,qword ptr [rsp+58h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  twinui_appcore!CCriticalFailureHandler::HandleFailure+ba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: twinui_appcore

IMAGE_NAME:  twinui.appcore.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  54503801

STACK_COMMAND:  ~18s; .ecxr ; kb

FAILURE_BUCKET_ID:  SHELL_COMPONENT_STARTUP_FAILURE_ERROR_CODE_ffffffff80270233_80270233_twinui.appcore.dll!CCriticalFailureHandler::HandleFailure

BUCKET_ID:  APPLICATION_FAULT_SHELL_COMPONENT_STARTUP_FAILURE_ERROR_CODE_ffffffff80270233_twinui_appcore!CCriticalFailureHandler::HandleFailure+ba

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:shell_component_startup_failure_error_code_ffffffff80270233_80270233_twinui.appcore.dll!ccriticalfailurehandler::handlefailure

FAILURE_ID_HASH:  {bc588def-f8dc-26b8-dac8-a057fb6557c4}

Followup: MachineOwner
---------

0:018> lmvm twinui_appcore
start             end                 module name
00007ffe`becf0000 00007ffe`bee20000   twinui_appcore   (pdb symbols)          downstreamstore\twinui.appcore.pdb\310246EA4A1E4BF8A48502B727A7376B1\twinui.appcore.pdb
    Loaded symbol image file: twinui.appcore.dll
    Image path: C:\Windows\System32\twinui.appcore.dll
    Image name: twinui.appcore.dll
    Timestamp:        Wed Oct 29 01:42:41 2014 (54503801)
    CheckSum:         0013A0E7
    ImageSize:        00130000
    File version:     6.3.9600.17415
    Product version:  6.3.9600.17415
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     TWINUI.APPCORE
    OriginalFilename: TWINUI.APPCORE.dll
    ProductVersion:   6.3.9600.17415
    FileVersion:      6.3.9600.17415 (winblue_r4.141028-1500)
    FileDescription:  TWINUI.APPCORE
    LegalCopyright:   Microsoft Corporation. All rights reserved.

Does this make any sense to anyone?

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

• Proposed as answer by MeipoXuMicrosoft contingent staff 5 hours 31 minutes ago

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

• Proposed as answer by MeipoXuMicrosoft contingent staff Friday, March 13, 2015 1:45 AM

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

• Proposed as answer by MeipoXuMicrosoft contingent staff Friday, March 13, 2015 1:45 AM
• Edited by Wieger1983 Sunday, March 15, 2015 7:09 AM made addition to answer (edit 1)

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

• Proposed as answer by MeipoXuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:45 AM
• Edited by Wieger1983 Sunday, March 15, 2015 7:09 AM made addition to answer (edit 1)
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator 21 hours 44 minutes ago

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

Edit 2 (03/24/2015):

See my latest post(s). The crashes keep popping up (sometimes it works a few time, then later it crashes again). Trying to isolate the problem... Should have tried using another PC/model earlier.

• Proposed as answer by MeipoXuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:45 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Monday, March 23, 2015 9:35 AM
• Unmarked as answer by Wieger1983 16 hours 57 minutes ago
• Unproposed as answer by Wieger1983 16 hours 57 minutes ago
• Edited by Wieger1983 16 hours 55 minutes ago see edit 2

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

Edit 2 (03/24/2015):

See my latest post(s). The crashes keep popping up (sometimes it works a few time, then later it crashes again). Trying to isolate the problem... Should have tried using another PC/model earlier.

• Proposed as answer by MeipoXuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:45 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Monday, March 23, 2015 9:35 AM
• Unmarked as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Unproposed as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Edited by Wieger1983 Tuesday, March 24, 2015 2:23 PM see edit 2

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

Edit 2 (03/24/2015):

See my latest post(s). The crashes keep popping up (sometimes it works a few time, then later it crashes again). Trying to isolate the problem... Should have tried using another PC/model earlier.

• Proposed as answer by MeipoXuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:45 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Monday, March 23, 2015 9:35 AM
• Unmarked as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Unproposed as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Edited by Wieger1983 Tuesday, March 24, 2015 2:23 PM see edit 2

Never mind. I've deinstalled Samba 3.6.25 and then reinstalled it... Maybe it was some inconsistent state of the Samba software or dependencies. Now it takes about 1 minute and 40 seconds for the desktop to appear and Explorer.exe does not crash.

Thanks anyway for your help.

Edit 1 (03/15/2015):

The network settings also seem to matter a lot. At the time of the reinstall of Samba 3.6.25 I had manual IPv4 settings in place for the ethernet adapter. It was foolish of me not to write those settings down somewhere.

The settings were not working at first but as I posted above: after reinstall they suddenly began working. I tested three times and all those times no crashes.

Though as soon as I changed the manual mode to DHCP-mode the crashes came again.

I'll try again Monday to figure out. I know I did something with WINS at first and later I put the domain name in DNS (like I already have in my home network environment).

We have multiple subnets and multiple VLANs.

I will post my findings here.

Edit 2 (03/24/2015):

See my latest post(s). The crashes keep popping up (sometimes it works a few time, then later it crashes again). Trying to isolate the problem... Should have tried using another PC/model earlier.

• Proposed as answer by MeipoXuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:45 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Monday, March 23, 2015 9:35 AM
• Unmarked as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Unproposed as answer by Wieger1983 Tuesday, March 24, 2015 2:21 PM
• Edited by Wieger1983 Tuesday, March 24, 2015 2:23 PM see edit 2

Hi Wieger1983,

I am glad the issue has been resolved and thanks for sharing the troubleshooting experience here.

Best r

Hi MeipoXu (and others),

The reinstall of Samba 3.6.25 helped a lot (it began working immediately as I posted earlier). So that was a big part of the solution.

But the second part - the manual network settings I had in place - also seem to be part of the solution.

But now I need to figure out which network settings are correct because I foolishly thought it was a one-factor-solution and just switched to DHCP mode and did not write down the settings I had in place for the network adapter.

Monday I will try and figure out which settings I had in place and then I will post what changes are needed to make it work.

Maybe it will help someone who is having the same problem.

Though there is not much to be found about this specific problem using a search engine as far as my searching skills go ;-)

Hi Wieger1983,

Thanks for updating and I am looking forward to the good news.

Much appreciation again

Best regards

Sorry for the delay in response.

I'm at a bit of a loss. I thought I had solved it (several times). But it keeps coming back.

Tried rejoining domain, fiddling with network settings, deinstalling and reinstalling Samba. It worked several times after trying several different things, but then comes back to 'haunt' us.

I've also tested the RAM and put in a different graphics card (or actually it does not really have a graphics *card* [Q963/Q965 chipset]).

The model used - dc7700 - is actually a model which does not have specific Windows 8.1 drivers. So I used Microsoft drivers, like the Basic Display adapter. Also tried Vista drivers.

I should have tried way earlier though, but I'm going to try and see if the problem is specific to the client PC (dc7700) or if it is really some (weird) problem with the server configuration.

So I am going to try and run Windows 8.1 on a totally different PC tomorrow. If that does works (and keeps working) then the server configuration cannot be the cause and it must be something with the client.

Hi Wieger1983,

How about the issue ,is there anything to update ?

Best regards

Yes, there is. Some server-side setting must be triggering the crash. Because I get exactly the same Application Crash error in a VM (on another PC) at profile creation start.

The non-LDAP Samba3 domain (NT PDC) *is* working with Windows 8.1. So tomorrow I'm going to copy that configuration (again) and step by step adding things to see which part of the configuration is the culprit.

I'll inform you of any progress. If I find the offending setting I will post it here.

I don't have any settings here but if I remember correctly I've set up my profile shares according to this wiki (the POSIX permissions):

https://wiki.samba.org/index.php/Samba_%26_Windows_Profiles#Profile_share_with_using_POSIX_ACLs

Only then I'm not using "Domain Users" but another group called 'samba' (which I enforce using: force group = samba).

• Edited by Wieger1983 23 hours 30 minutes ago linked the Samba Wiki URL

Hi Wieger ,

Thanks for updating and I am looking forward to your good news .

Best regards

Yes, there is. Some server-side setting must be triggering the crash. Because I get exactly the same Application Crash error in a VM (on another PC) at profile creation start.

The non-LDAP Samba3 domain (NT PDC) *is* working with Windows 8.1. So tomorrow I'm going to copy that configuration (again) and step by step adding things to see which part of the configuration is the culprit.

I'll inform you of any progress. If I find the offending setting I will post it here.

I don't have any settings here but if I remember correctly I've set up my profile shares according to this wiki (the POSIX permissions):

https://wiki.samba.org/index.php/Samba_%26_Windows_Profiles#Profile_share_with_using_POSIX_ACLs

Only then I'm not using "Domain Users" but another group called 'samba' (which I enforce using: force group = samba).

• Edited by Wieger1983 Tuesday, March 31, 2015 7:50 AM linked the Samba Wiki URL

Yes, there is. Some server-side setting must be triggering the crash. Because I get exactly the same Application Crash error in a VM (on another PC) at profile creation start.

The non-LDAP Samba3 domain (NT PDC) *is* working with Windows 8.1. So tomorrow I'm going to copy that configuration (again) and step by step adding things to see which part of the configuration is the culprit.

I'll inform you of any progress. If I find the offending setting I will post it here.

I don't have any settings here but if I remember correctly I've set up my profile shares according to this wiki (the POSIX permissions):

https://wiki.samba.org/index.php/Samba_%26_Windows_Profiles#Profile_share_with_using_POSIX_ACLs

Only then I'm not using "Domain Users" but another group called 'samba' (which I enforce using: force group = samba).

• Edited by Wieger1983 Tuesday, March 31, 2015 7:50 AM linked the Samba Wiki URL

Yes, there is. Some server-side setting must be triggering the crash. Because I get exactly the same Application Crash error in a VM (on another PC) at profile creation start.

The non-LDAP Samba3 domain (NT PDC) *is* working with Windows 8.1. So tomorrow I'm going to copy that configuration (again) and step by step adding things to see which part of the configuration is the culprit.

I'll inform you of any progress. If I find the offending setting I will post it here.

I don't have any settings here but if I remember correctly I've set up my profile shares according to this wiki (the POSIX permissions):

https://wiki.samba.org/index.php/Samba_%26_Windows_Profiles#Profile_share_with_using_POSIX_ACLs

Only then I'm not using "Domain Users" but another group called 'samba' (which I enforce using: force group = samba).

• Edited by Wieger1983 Tuesday, March 31, 2015 7:50 AM linked the Samba Wiki URL

Using exactly this now from the Samba wiki:

# mkdir -p /srv/samba/profiles/
# chmod 1770 /srv/samba/profiles
# chgrp "Domain Users" /srv/samba/profiles

In smb.conf this:

[Profiles]
 path = /srv/samba/Profiles/
 read only = no
 store dos attributes = Yes
 create mask = 0600
 directory mask = 0700
 profile acls = yes
 csc policy = disable

Problem is: the user who is logging in appears to need "Domain Users" as primary group. Specifying "Domain Users" as secondary group does not work and crashes explorer.exe.

Still. When using "Domain Users" as primary group profile creation seems kind of slow. Do not know what is causing that slowness. "force group = Domain Users" with or without quotes does not relieve the issue, so it seems.

Edit: Tried same thing (from the wiki) at home. There it works quite well and it also works with "Domain Users" as secondary group at home. No need for a primary group "Domain Users" for it to work.

So it must be something with the group mapping. I'll have another look tomorrow.

• Edited by Wieger1983 13 hours 24 minutes ago new finding

Using exactly this now from the Samba wiki:

# mkdir -p /srv/samba/profiles/
# chmod 1770 /srv/samba/profiles
# chgrp "Domain Users" /srv/samba/profiles

In smb.conf this:

[Profiles]
 path = /srv/samba/Profiles/
 read only = no
 store dos attributes = Yes
 create mask = 0600
 directory mask = 0700
 profile acls = yes
 csc policy = disable

Problem is: the user who is logging in appears to need "Domain Users" as primary group. Specifying "Domain Users" as secondary group does not work and crashes explorer.exe.

Still. When using "Domain Users" as primary group profile creation seems kind of slow. Do not know what is causing that slowness. "force group = Domain Users" with or without quotes does not relieve the issue, so it seems.

Edit: Tried same thing (from the wiki) at home. There it works quite well and it also works with "Domain Users" as secondary group at home. No need for a primary group "Domain Users" for it to work.

So it must be something with the group mapping. I'll have another look tomorrow.

• Edited by Wieger1983 Wednesday, April 01, 2015 5:56 PM new finding

Using exactly this now from the Samba wiki:

# mkdir -p /srv/samba/profiles/
# chmod 1770 /srv/samba/profiles
# chgrp "Domain Users" /srv/samba/profiles

In smb.conf this:

[Profiles]
 path = /srv/samba/Profiles/
 read only = no
 store dos attributes = Yes
 create mask = 0600
 directory mask = 0700
 profile acls = yes
 csc policy = disable

Problem is: the user who is logging in appears to need "Domain Users" as primary group. Specifying "Domain Users" as secondary group does not work and crashes explorer.exe.

Still. When using "Domain Users" as primary group profile creation seems kind of slow. Do not know what is causing that slowness. "force group = Domain Users" with or without quotes does not relieve the issue, so it seems.

Edit: Tried same thing (from the wiki) at home. There it works quite well and it also works with "Domain Users" as secondary group at home. No need for a primary group "Domain Users" for it to work.

So it must be something with the group mapping. I'll have another look tomorrow.

• Edited by Wieger1983 Wednesday, April 01, 2015 5:56 PM new finding

Using exactly this now from the Samba wiki:

# mkdir -p /srv/samba/profiles/
# chmod 1770 /srv/samba/profiles
# chgrp "Domain Users" /srv/samba/profiles

In smb.conf this:

[Profiles]
 path = /srv/samba/Profiles/
 read only = no
 store dos attributes = Yes
 create mask = 0600
 directory mask = 0700
 profile acls = yes
 csc policy = disable

Problem is: the user who is logging in appears to need "Domain Users" as primary group. Specifying "Domain Users" as secondary group does not work and crashes explorer.exe.

Still. When using "Domain Users" as primary group profile creation seems kind of slow. Do not know what is causing that slowness. "force group = Domain Users" with or without quotes does not relieve the issue, so it seems.

Edit: Tried same thing (from the wiki) at home. There it works quite well and it also works with "Domain Users" as secondary group at home. No need for a primary group "Domain Users" for it to work.

So it must be something with the group mapping. I'll have another look tomorrow.

• Edited by Wieger1983 Wednesday, April 01, 2015 5:56 PM new finding

Profile folder wasn't the culprit. Now I'm very very sure I've found the real culprit ;-)

I'm using KiXtart for my login script. KiXtart's INGROUP function appears to be the 'cause' of my problems. Maybe because we do not allow anonymous binds or regular users access to the LDAP tree.

If I don't use INGROUP in my KixTart script then it all works... So I will have to find another solution to checking group membership. I know of a few possibilities.

Or I will have to configure the OpenLDAP server with more lenient ACL entries.

Anyway, I know now how to keep it from crashing. So for me it's solved.

• Marked as answer by Wieger1983 13 hours 24 minutes ago

Profile folder wasn't the culprit. Now I'm very very sure I've found the real culprit ;-)

I'm using KiXtart for my login script. KiXtart's INGROUP function appears to be the 'cause' of my problems. Maybe because we do not allow anonymous binds or regular users access to the LDAP tree.

If I don't use INGROUP in my KixTart script then it all works... So I will have to find another solution to checking group membership. I know of a few possibilities.

Or I will have to configure the OpenLDAP server with more lenient ACL entries.

Anyway, I know now how to keep it from crashing. So for me it's solved.

• Marked as answer by Wieger1983 Thursday, April 02, 2015 5:56 PM

Profile folder wasn't the culprit. Now I'm very very sure I've found the real culprit ;-)

I'm using KiXtart for my login script. KiXtart's INGROUP function appears to be the 'cause' of my problems. Maybe because we do not allow anonymous binds or regular users access to the LDAP tree.

If I don't use INGROUP in my KixTart script then it all works... So I will have to find another solution to checking group membership. I know of a few possibilities.

Or I will have to configure the OpenLDAP server with more lenient ACL entries.

Anyway, I know now how to keep it from crashing. So for me it's solved.

• Marked as answer by Wieger1983 Thursday, April 02, 2015 5:56 PM

Hi Wieger1983,

So the issue is caused by the corrupted profile folder .

I am glad the issue has been resolved and thanks for updating .

Best regards