Well, this is bad. I store all of my business contacts in outlook, and since updating to 14291, my outlook contacts are EMPTY! I have tried going to the contacts settings and selected "sync" to no avail. The account shows up, and I get my calendar appointments - just no contacts which means NO PHONE NUMBERS! Any suggestions?
950xl has lost all outlook contacts after 14291 update!
- Thread starter pdch
- Start date
abhishek singh21
Active member
insiders preview always means such bugs are inevitable , as of now post the issue on feedback app , try a hard reset or if you have already done it roll back to .164
coolj40041
New member
Beta testing when your business is on the line? That's one stock I'd like to short. Hope you backed up your contacts on the cloud somewhere. My advice, same as previous post, get out of Insider Preview. .like now.
Posted via the Windows Central App for Android
Posted via the Windows Central App for Android
You can try hard reset and restore from backup. Hopefully you still have a backup.
I saved all my contacts to My Gmail account. So whenever I add my Gmail account in outlook, they all come back.
GL!
I saved all my contacts to My Gmail account. So whenever I add my Gmail account in outlook, they all come back.
GL!
My contacts aren't lost, just wont push to phone. They still exist on my other devices. In fact, I can still text through my phone from my laptops/pcs. I could force load them back to the device, but want to try to figure out what is happening.
FYI, there are apparently a lot of users having this problem on multiple builds of windows phone (including release). There are multiple threads on MS website.
Did a hard reset after trouble shooting with Microsoft support. They had no other suggestions, but the reset did fix the problem.
Been having the same problem. Did another hard reset last night and I still don't have my Outlook contacts. This is complete BS!
Corwin_Amber1
New member
Not BS, you opted in to receive fast ring insider builds. it clearly says the fast ring builds can cause problems with your phone. The only BS is that you failed to read the warnings or just didn't care about them. If you want stability, use the WDRT and go back to a production build.
Dude, what are you talking about? I never said ANYTHING about being on the fast ring. As a matter of fact, I'm on the regular production build and not even enrolled in Insider at all on my phone (have been in the past however). This site is insane with folks jumping the gun to tell people what they can and can't complain about. Or jumping to conclusions about things in general. Me expecting to have my contacts sync properly with Outlook (of all things) is not insane on a production build that is being released to the masses.
Matter of fact, there was already another user in this thread that said it's occurring on multiple builds (to include release), so that should've been enough indication to you that it's not just folks on Insider. You guys on your high horses is utter crap and as long as I've been using Windows Mobile, Phone, etc. (since my Cingular 2125 and PDA's before that) I've never seen the amount of useless, conclusion drawing users as there are on this site (and I was a proud, contributing member of XDA before coming here). Get a clue, and if you're just going to jump the gun on everything, or be quick to insult folks intelligence, you're not needed here or on any forum. I doubt you dudes would talk so sly if you weren't on your computer typing. Believe me, you want none of this in your face (in person, meaning real life)....douchebags.
I do realize this is in a thread about an Insider build, but I merely commented in this thread so that the OP would know that this problem is widespread and not just on Insider.
The OP said he had the problem after updating to Redstone (via build number). You said you had the same problem. After reading your last post I see you don't have the "same" problem. Perhaps you should have said you had a similar problem on a different build. That actually would have been much more clear and way more helpful.
I didn't "jump to a conclusion" I just assumed that the information you provided was accurate. Your information was misleading which was the cause of the confusion
That's s certainly fair enough and I agree that I should've been clear about the fact that I'm on a different build. But everyone really does need to stop with the "you're on insider" defense when there's basic functionality that has problems. It applies in a lot of situations and I defend Microsoft to the fullest all of the time. But proper synching of contacts isn't trivial or something newly implemented. No reason it should be broken.... on any build. Especially when your Google contacts sync fine. It just doesn't look good.
I agree with you about the insider thing which is why I only remind people they are on an insider build when that's the premise of the thread or comment. Some people do seem to jump to conclusions needlessly. It would be so much less confusing if people listed their firmware and build with any complaint. I had actually suggested that people say whether or not the thread pertained to an insider build or production build and someone (not you) gave me a boat load of crap over it. It just seems that more information is always better then less information when discussing problems like this.
I'm on the fast ring, and yes, I know I'm "on insider", but I have the same problem, and I really don't know why they release builds that are more buggy than the last. From MS point of view, it probably makes sense, as they get some quality testing results, quickly and in bulk, but from a usability point of view (i.e.: mine) it's sometimes quite annoying.
Cortana and voice input has not worked for me for about 3 weeks, last two builds I think. I can live with that, but on the last build where we cannot backup/hard reset, it was annoying to lose all my outlook contacts and calendars. I had to remove my outlook account completely to get it limping again.
Should I hope the next build is better? You bet!
Will I be disappointed if it's not? You bet!
(& Yes, I'm on Insider...I signed myself up for all this pain, so I only have myself to blame. )
Cortana and voice input has not worked for me for about 3 weeks, last two builds I think. I can live with that, but on the last build where we cannot backup/hard reset, it was annoying to lose all my outlook contacts and calendars. I had to remove my outlook account completely to get it limping again.
Should I hope the next build is better? You bet!
Will I be disappointed if it's not? You bet!
(& Yes, I'm on Insider...I signed myself up for all this pain, so I only have myself to blame.
)
Last edited:
I'm on the fast ring, and yes, I know I'm "on insider", but I have the same problem, and I really don't know why they release builds that are more buggy than the last. From MS point of view, it probably makes sense, as they get some quality testing results, quickly and in bulk, but from a usability point of view (i.e.: mine) it's sometimes quite annoying.
Cortana and voice input has not worked for me for about 3 weeks, last two builds I think. I can live with that, but on the last build where we cannot backup/hard reset, it was annoying to lose all my outlook contacts and calendars. I had to remove my outlook account completely to get it limping again.
Should I hope the next build is better? You bet!
Will I be disappointed if it's not? You bet!
(& Yes, I'm on Insider...I signed myself up for all this pain, so I only have myself to blame.
I have a question for you since I'm not in the fast ring. You said each build is more buggy than the last. So is it really more buggy (same bugs plus new ones) or just different buggy (old bugs fixed but replaced by new ones), or maybe some of each?
A bit of each. Some things improve, more functionality in mail and calendar for example. Windows Hello got a LOT faster and more reliable than when I first had the phone. These are welcomed and the good part of Insider.
But other things are introduced or broken and not (yet) fixed after 2-3 builds.
1. Tap on notification on lock screen presents login pad... but NO DIGITS shown to tap! Need to sleep-rewake screen with Power button to get the numbers to show. Last 2 builds.
2. Launch camera app flickers black screen momentarily. This was introduced 3 builds ago, not fixed yet. Never had this issue in the first 3 months.
3. Long press Cortana does nothing - no speech input available. However, recognises "Hey Cortana", then does nothing.2 or 3 builds. Cortana USED to work 100% for me, now I don't use it at all.
4. Microphone input fails immediately, with double-beep and message "Try again" every time, last 2 builds. I USED to use this for nearly all my SMS message input, now have to use keyboard 100%.
5. Cannot seem to install language packs - last 2 builds, plus a build I had late December, so the bug went away, but them came back!
6. Backup and restore broken in last build (which they told us about, but released the build anyway) If you run a backup under 14291.1001, your backup is corrupted and cannot restore in future.
7. Outlook account became corrupted; contacts and calendar entries were lost from phone. This one annoyed me most because I could not hard-reset phone (due to #6) and I had to fiddle for a while to get it working.
But, I am on Insider, so I am prepared to experience these things, and have of course submitted them all via Feedback.
But other things are introduced or broken and not (yet) fixed after 2-3 builds.
1. Tap on notification on lock screen presents login pad... but NO DIGITS shown to tap! Need to sleep-rewake screen with Power button to get the numbers to show. Last 2 builds.
2. Launch camera app flickers black screen momentarily. This was introduced 3 builds ago, not fixed yet. Never had this issue in the first 3 months.
3. Long press Cortana does nothing - no speech input available. However, recognises "Hey Cortana", then does nothing.2 or 3 builds. Cortana USED to work 100% for me, now I don't use it at all.
4. Microphone input fails immediately, with double-beep and message "Try again" every time, last 2 builds. I USED to use this for nearly all my SMS message input, now have to use keyboard 100%.
5. Cannot seem to install language packs - last 2 builds, plus a build I had late December, so the bug went away, but them came back!
6. Backup and restore broken in last build (which they told us about, but released the build anyway) If you run a backup under 14291.1001, your backup is corrupted and cannot restore in future.
7. Outlook account became corrupted; contacts and calendar entries were lost from phone. This one annoyed me most because I could not hard-reset phone (due to #6) and I had to fiddle for a while to get it working.
But, I am on Insider, so I am prepared to experience these things, and have of course submitted them all via Feedback.
Corwin_Amber1
New member
J, regarding number 6, I am not sure that this is the case when you are not hard resetting while on this build (https://blogs.windows.com/windowsex...nsider-preview-build-14291-for-pc-and-mobile/). I think the backups are fine. But yes, it is a little unclear from the exact wording, you could understand that. Do you know more about it, I mean, have you expierenced it?
I think I even did backups on this build before I WDRTed back to TH to get a newer Firmware (16082). It restored just fine. And I am quite sure I came from 14291.
I think I even did backups on this build before I WDRTed back to TH to get a newer Firmware (16082). It restored just fine. And I am quite sure I came from 14291.
No, I haven't experienced this, I just saw the following in the build announcement, and thought it look liked opening up a world of pain.
I figure (fingers crossed) it will be fixed in the next build, but as we know, that can be a bit hit and miss. I usually hard reset each build but will hold off until I hear it's fixed, I think.
Do you experience any of the other bugs I have? I've always thought that everyone on Fast Ring would have a similar experience to me.
I figure (fingers crossed) it will be fixed in the next build, but as we know, that can be a bit hit and miss. I usually hard reset each build but will hold off until I hear it's fixed, I think.
Do you experience any of the other bugs I have? I've always thought that everyone on Fast Ring would have a similar experience to me.
I don't think that what you're suggesting is such a bad idea honestly. At least listing the build information would help make things more clear. More information NEVER hurts. And my apologies for flying off the hinge. Frustration got the best of me.
Similar threads
Trending Posts
-
These Manor Lords upgrades are so overpowered you'd be crazy not to use them- Started by Windows Central
- Replies: 0
-
If Qualcomm really wants to beat Apple it needs an 'X Ultra' to challenge the M3 Max, but will it make one?
- Started by Windows Central
- Replies: 0
Facebook
Twitter
Instagram