Windows 10 repair Microsoft Solitaire Collection

Log Name:      Application

Source:        Application Error

Date:          3/23/2016 8:02:16 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-QFD54E9

Description:

Faulting application name: Solitaire.exe, version: 1.0.0.0, time stamp: 0x56e09278

Faulting module name: SharedLibrary.dll, version: 1.0.23115.1, time stamp: 0x55a642fb

Exception code: 0x00001007

Fault offset: 0x00000000003f5317

Faulting process id: 0xf0

Faulting application start time: 0x01d1855edf4fdd31

Faulting application path: C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_3.8.3092.0_x64__8wekyb3d8bbwe\Solitaire.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.NET.Native.Framework.1.1_1.0.23115.0_x64__8wekyb3d8bbwe\SharedLibrary.dll

Report Id: 49b16a63-5df3-49cf-b154-76a1740a0d85

Faulting package full name: Microsoft.MicrosoftSolitaireCollection_3.8.3092.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-03-24T00:02:16.240626500Z" />

    <EventRecordID>8913</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-QFD54E9</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Solitaire.exe</Data>

    <Data>1.0.0.0</Data>

    <Data>56e09278</Data>

    <Data>SharedLibrary.dll</Data>

    <Data>1.0.23115.1</Data>

    <Data>55a642fb</Data>

    <Data>00001007</Data>

    <Data>00000000003f5317</Data>

    <Data>f0</Data>

    <Data>01d1855edf4fdd31</Data>

    <Data>C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_3.8.3092.0_x64__8wekyb3d8bbwe\Solitaire.exe</Data>

    <Data>C:\Program Files\WindowsApps\Microsoft.NET.Native.Framework.1.1_1.0.23115.0_x64__8wekyb3d8bbwe\SharedLibrary.dll</Data>

    <Data>49b16a63-5df3-49cf-b154-76a1740a0d85</Data>

    <Data>Microsoft.MicrosoftSolitaireCollection_3.8.3092.0_x64__8wekyb3d8bbwe</Data>

    <Data>App</Data>

  </EventData>

</Event>

Microsoft Solitaire games working even after I installed Windows 10 - Quit Working last week.

Is there a fix for this?

Please let me know

Hi Jim,

I found the following site that has a pretty good guide to creating a new account.

http://www.techbout.com/fix-corrupt-user-profile-windows-10-9139/

After you've created the new account, you will have to delete the old one before you can associate your new account with your Microsoft Live account, as the Live account can only be linked to one local PC account. If you have any problems when you get to that stage, then ask back here again. :)

Geoff

Well it looks like you might have something there ,next question is how do I create a new profile?? I'm not that good with this thing ???

thank you for any help you might be able to give ,Jim

The only way that you are going to get the Solitaire Collection working again is to create a new User Profile.

I had to do this when it stopped working for me. It's not too much of a problem, but can take a while, especially if you have a lot of files to copy across to the new account from your old one.

I wouldn't worry about your wins as these are stored to your online Microsoft account, so as soon as you log back in to the Collection, your previous records are restored.

Whilst my Solitaire Collection is now working as it should, I've now developed a problem with Candy Crush Soda; again, it works on my girlfriend's account, but refuses to run on mine. I think that the Apps that run exclusively from the Start window are the only ones affected by these issues and that there is obviously a serious flaw in the way the interface has been designed and coded by Microsoft. They should be doing something about it, rather than just totally ignoring their paying public and brushing the whole thing under the carpet. I know my impressions of Windows 10 that were initially complementary have taken a nosedive because of these issues; if these seemingly simple issues cannot be resolved, what other potentially harmful coding errors are there lurking beneath the surface of the O/S?