Fellow Surface Pro / MS abused customers:
On my second SP4 I7, 8 Ram, 252 GB, with the keyboard and dock.
Frist was exchanged at Staple due to the “plugged in not charging” thing.
This one about 15 months old.
Flickering, comparatively minor than some seen on You tube started about 6 weeks ago.
So much history over at least 2 MS HW products.
Going to MS tech support I was transferred twice with no “warning” to _________ (I want to protect the only person that was somewhat helpful.
She spent hours over several days with me checking all the hardware and software.
Never got the “power / volume up (or Down) procedure to work to get to a thumb drive reboot.
She is convinced the Flicker a software issue.
She sent me a USB 3
Win Pro EN/FR/ES Disk Kit Direct USB Surface Pro4 RS2
Back-up Media, Not for Re-sale
She called on a Friday and we got disconnected!
The on 11/14 I got this voicemail-
Hi there Victor, good afternoon this is _____ from MS Tech support. I’m calling back to make a follow-up….
First of all I’d like to apologize. I wasn’t able to call back. I didn’t know this case that I created for your was ‘auto closed’…in our system. There was a system glitch.
Got your feedback and sensed your frustration. Let’s continue to trouble shoot…..
NOTE- I NEVER GOT A CASE # OR A CAL BACK # OR A E-MAIL ADDRESS TO A LIVE PERSON.
I do not know if I’ll ever here from MS again on this.
I had reset(?) My whole computer and reinstalled everything.
My only “reward” is that I have more room on my C drive as I put more programs on my external drive.
Sent this 11/15:
Got a voice mail from [email protected] Surface Tech Support last night 11/14.
______ can you call me today? 2525714735
Otherwise 11/20 or 11/21 @ 0800
Please leave me another voice mail and tell me my case #.
This is the response:
BAY004-MC1F55.hotmail.com rejected your message to the following email addresses:
Microsoft account team ([email protected])
Your message couldn’t be delivered. It appears that the email address you sent your message to wasn’t found at the destination domain, or the recipient’s mailbox is unavailable. The email address might be misspelled or it might not exist. Try to fix the problem by doing one or more of the following:
- Send the message again. Before you do, delete and retype the complete address. If your email program automatically suggests an address to use don’t select it.
- Clear the recipient Auto-Complete List entry in your email program by following the steps in this article. Then resend the message, but before you do, delete and retype the complete address. If your email program suggests an address to use don’t select it.
- Contact the recipient by some other means (by phone, for example) to confirm you’re using the right address. Ask them if they’ve set up an email forwarding rule that could be forwarding your message to an incorrect address.
If you’re still unable to fix the problem, ask the recipient to tell their email admin about the problem, and give them the server that reported the error below.
For Email Admins
When Office 365 tried to send the message, the external email server returned the error below. This error was reported by an email server outside Office 365, and if the sender is unable to fix the problem by correcting the recipient’s email address or clearing the Auto-Complete List entry, then it’s likely a problem that only the recipient’s email admin can fix.
- Check the error for information about where the problem is happening. For example, look for a domain name. The domain name will tell you which organization was responsible for the error. The recipient’s email server could be causing the problem, or it could be due to a third-party service that your organization or the recipient’s organization is using to process or filter email messages.
- If you can’t fix the problem, contact the responsible party’s email admin. This could be the recipient’s email admin, your smart host service admin, or someone similar. Give them the error and the name of the server that reported the error to help them troubleshoot the issue.
Unfortunately, Office 365 support is unlikely to be able to help with these kinds of externally reported errors.
BAY004-MC1F55.hotmail.com gave this error:
Remote server returned unknown recipient or mailbox unavailable -> 550 Requested action not taken: mailbox unavailable
Sent the original msg. to some MS support groups
This is one answer:
|HiepHo85 has replied to the question Screen shaking, that you are following in Microsoft Community.|
|Goode evening, I wonder if you referred to me as _____, but that is not my name. You asked me to call you back and mention “case number”. I don’t have a case number yet|
So “good luck” to us all