Microsoft updated the Mail, Calendar and People App in the Windows Store on June 26. After that update, a number of people, including myself, found that the app would open but then “crash” immediately. It still would be running in the background, but would not display the default screen. I saw this on 4 Windows 8.1 computers. I checked the 2 computers running Windows 8.1 that had not yet been updated with the latest revision of the app and they worked fine. I upgraded to the new App release on one of these two computers, and as expected, the crashing behavior started.
After reading the initial complaints that started appearing in the Microsoft Forums http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/windows-store-app-update-breaks-people-app/cd14abd2-1bc5-40d8-9e09-a51c66bfea2a I started digging into this. My hunch, reinforced by my logs and the log from another user, was that something in the social media integration function was causing the issue.
I found that link to control which social media accounts were linked to my Microsoft ID: https://profile.live.com/cid-27a6342ef735cc0f/Services/?view=manage
It turns out that the Twitter integration was causing the issue for me. After removing the Twitter integration, the App functions as it should and displays properly.
And yes, the Facebook Connect piece is now deprecated, but that was not causing the crashes.
I’m not 100% convinced that Microsoft has escalated the issue to the team that owns the app.
I keep trying to get the Start menu on Windows 10 to show what I want and not what Microsoft wants. I turned off the first two entries in Personalization, Start. I especially do NOT want app or content suggestions in my Start menu. I suppose this is yet another bug. But it is most annoying that I can’t get the Start menu to look anything like the Start menu in Windows 8.1 on my tablet. And I LIKE the Start menu on tablets in 8.1. The Windows 10 Start menu was built for Phones and for folks that use Portrait View.
If you find that you can no longer get the Start menu to display in 10130, you’ll have to not opt out of what Microsoft wants. At least for now.
I hadn’t planned to spend all night Friday and most of Saturday morning dealing with annoying Insider Preview Windows 10 issues. But that happened on my Surface Pro original.
It all started yesterday afternoon when I dug into why some June updates were sitting in the “Downloading” status and were stuck. Reboots didn’t help, just stuck at 53% for hours and hours. So I tried to reinstall 10130 from ISO over the top of 10130 to see if I could do an in place upgrade to repair whatever was wrong. After a couple of hours, I thought I was going to be ok, had two reboots, and got to a prompt that required me to select NEXT. I’d hit NEXT either by touch or type keyboard and the tablet would reboot. Rinse and repeat. Held down the power button to insure totally off. Powered on, got to select NEXT. Boom. Rinse and repeat.
So last night it was time to nuke and pave. I decided to see what a real upgrade over 8.1 Pro might be like for a typical end user.
I created a USB recovery drive for my original Surface Pro using the downloadable bits online. I did the volume down/power thing and booted off the USB and ran the setup. It took forever. And that was Windows 8.0. I couldn’t install 8.1 from the Store without installing Windows Updates. 142 of them. I have a fast connection, but that took hours. Went to bed. Got up early and updates were installed, rebooted a couple of times, found more updates, more reboots. Went to the Store and started the 8.1 updates. Went out and did some grocery shopping. Couple of hours later 8.1 was installed. Went to the Store, My Apps, got the ones I needed. Note that they did NOT appear on the Start Screen with the indicator to download so I had no familiar Start Screen layout. My sync settings WERE correct. Maybe because this tablet once had W10 on it this sync piece no longer applies when you first power up a “new” computer. Anyway, I downloaded the apps and they landed in their designated layout on Start.
Went to insider.microsoft.com as again, I wanted to see what the end user experience would be upgrading from 8.1. 10074 was offered, not 10130, I guess because of all the issues people have been reporting with 10130. So two hours later, 10074 is installed. And my Start menu is replaced by what I guess is the “default” arrangement for Start. My carefully arranged app tiles from 8.1 totally ignored.
Now from within 10074, Windows Update, I have to install the offered 10130.
Here’s a trick if you are desperately trying to get your hands on a hotfix from Microsoft that requires you to contact support and are getting a run around. Do this at your own risk. Make sure you need the fix and have created a restore point if things go wrong. I won’t support you and Microsoft won’t support you.
You need to know the KB number of the hotfix you need. Find a hotfix (OK, I’ll do it for you) for a different item where the download is available without going through contacting support again. Like http://support.microsoft.com/en-us/kb/2955769
Click the Hotfix Download Available button.
After selecting that link, an URL will appear in the address bar like https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2955769&kbln=en-us
Copy the URL in the address bar and paste into Notepad.
Replace the KB 2955769 number with the one you are having difficulty getting. So that you have a link like https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=XXXXXXXX&kbln=en-us where XXXXXXXX is the KB number you are having trouble getting.
Now you can get your hotfix.
Again, I won’t support you and Microsoft won’t support you, but maybe you can fix your problem without multiple calls to support and incompetent poorly trained support agents.
Miracast adapters like the Microsoft Wireless Display Adapter and the Netgear PTV3000, etc. negotiate a connection with the source device. To do this, they broadcast a message that basically announces that they are available for a connection. To do this, the adapter will use one of the three non-overlapping 2.4GHz 802.11 channels (1, 6 and 11) which in essence are the lowest common denominator and would be the most broadly available and used channels. (For this reason, if you are on a device that allows 5GHz only connections and suppresses 2.4 GHz, you cannot connect). Therefore, 2.4GHz is a requirement to negotiate a connection using Miracast.
1. If 2.4GHz is the only frequency supported by your router, then issues might occur due to saturated channels from nearby routers in your environment. You might try changing the channel on your router to see if conditions improve. To see all the Wireless channels nearby, open a cmd prompt and type:
netsh wlan show networks mode=BSSID [press Enter]
2. If you are connected to your router using a 5GHz channel, the Miracast frequency can be negotiated to use 5GHz (but remember, the negotiation initiates over 2.4 GHz).
3. If you are not connected to a WiFi network, the Miracast connection will always be negotiated on 2.4 GHz
A Miracast session creates a virtual, second network on a direct, peer to peer basis between your host computer/device and the target Miracast display/Miracast enabled TV/Miracast adapter. You can see this in the Network and Sharing Center in Windows 8.1 after a connection is successfully made: