[MCPE-12300] Version 13.1 will not open on secondary windows user account Created: 02/Jan/16 Updated: 21/Aug/17 Resolved: 21/Aug/17 |
|
| Status: | Resolved |
| Project: | Minecraft (Bedrock codebase) |
| Component/s: | None |
| Affects Version/s: | 0.13.0 Beta 1, 0.13.0, 0.13.1 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Justin Wurm | ||
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Confirmation Status: | Unconfirmed |
| Platform: | Windows |
| Description |
|
I posted this issue on the forums and haven't had anyone answer it yet, and I've reached the end of my Google-Fu. Sorry if this doesn't belong here, but I'm not sure where to go for help anymore! I bought the windows 10 version and installed it on the family PC under my user account, as well as my son's user account (logging into the store as myself and installing it. Both of us were able to play within our user accounts, with no problems. It looks like after the upgrade to 13.1, only one user can access Minecraft. At first, only my son's user name could open the app; when I clicked on it in my user name, nothing happened. It didn't seem like it even attempted to open. I restored my computer to a point a few days before that, and we could both get in again. It looks like when one account is updated to 13.1, the other account will no longer work. Right now, I can get in, but my son cannot open the app. Any help anyone can give me would be greatly appreciated! Thanks in advance! I tried a few times to uninstall the app and reinstall it, both on my account and my son's, to no avail. below are some of the errors I'm getting in the event viewer: This is under Microsoft - ActivateApplicationForContractByAppIdAsUserWithHost of the app Microsoft.MinecraftUWP_8wekyb3d8bbwe!App for the Windows.Launch contract failed with Invalid value for registry. This is one that came up yesterday, but I don't know if it was related to trying unsuccessfully to open Minecraft, it is under Windows Logs --> Applications Faulting application name: Minecraft.Win10.DX11.exe, version: 0.13.1.0, time stamp: 0x56622efa In DxDiag, this comes up in the diagnostics section. It's repeated several times. --------------- Windows Error Reporting: Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.MinecraftUWP_0.131.0.0_x64__8wekyb3d8bbwe P2: praid:App P3: 0.13.1.0 P4: 56622efa P5: Minecraft.Win10.DX11.exe P6: 0.13.1.0 P7: 56622efa P8: c0000005 P9: 00000000004572a7 P10: If anyone needs anything else from me, please let me know. Thanks again for the help!! |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 21/Aug/17 ] |
|
This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+) |
| Comment by gatharian [ 01/Mar/16 ] |
|
Does this bug affect 0.14.0? If so please respond. |
| Comment by Justin Wurm [ 24/Jan/16 ] |
|
To close the loop on this issue, I was able to get Minecraft (Windows 10 Version) to start working again, by deleting my son's user account through the Windows Control Panel, and then adding it back in and reinstalling Minecraft through the Windows Store. I don't know if it was a corrupt user profile, or if the upgrade to version 13.1 messed something up, but regardless, it's fixed now. Thanks! |
| Comment by Justin Wurm [ 20/Jan/16 ] |
|
Thank you, Aleksandra. By the forums, I meant that I had posted this on the Minecraft PE troubleshooting forums, as I wasn't sure if this was considered a bug or something on my end. Nobody offered any suggestions there, so I figured I'd report it as a potential bug here. I've also been working with someone on the Microsoft Community to try to solve the issue, to no avail. That post and the things we've tried to do so far are over at: Thanks! |
| Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 20/Jan/16 ] |
|
Sorry - we do not check forums (which forums do you mean?) for bugs. |
| Comment by Justin Wurm [ 02/Jan/16 ] |
|
Thanks for the response! I was wondering this myself, but it does appear to correspond to the 13.1 update. I've no proof that it actually is related, though, as it looks like there may have been some windows updates around the same time. I've also tried adjusting permissions for various folders, but had no real idea what I was doing, and it didn't seem to affect the issue. |
| Comment by gatharian [ 02/Jan/16 ] |
|
This appears to be an issue on Microsoft's end and not the game itself. |