patch | Windows Central

What could've been

This is Microsoft’s original vision for the Lumia 950 series

All in on AI

Did Microsoft shift to an AI-focused strategy because of Google?

Clamshell vs. Kickstand

Surface Laptop vs. Surface Pro: Spec showdown and form factor wars

Windows Central Digital Offers

Break into a cybersecurity career with this $69 certification bundle!

Microsoft vs Dell

Quick comparison of the new Surface Pro and Dell's XPS 15

Both great devices

Does the new Surface Pro really edge out the cheaper Surface Pro 4?

All the apps

Hey you! Don’t forget about all of Windows Central’s apps.

Microsoft mixes up Beam

Microsoft's 'Beam' service is getting a rebrand, say hi to 'Mixer'

Star Wars hits the big 4-0

Celebrate Star Wars' birthday with these great gifts!

Pro vs. Laptop

Should you buy Microsoft's Surface Pro or Surface Laptop?

Love/hate relationship

8 things you'll love about new Surface Pro – and 3 things you'll hate

Monkey see monkey do

Is Microsoft's Fluent Design a clone of Google's Material Design?

Surface FTW

Surface Pro beats iPad Pro in a tech spec comparison — by a mile

Cast your vote ...

Will you buy Microsoft's new Surface Pro? (poll)

The pinnacle of Surface

Why isn't the new Surface Pro named 'Surface Pro 5?'

Stay cool look cool

Introducing the new Windows Central 'Colors T-Shirt,' now ready to order!

Missing the future

Why Microsoft's new Surface Pro doesn't have a USB Type-C port

All new for 2017

Meet the new Microsoft Surface Pro!

Tilt and shift

New Microsoft Surface Pen: Everything you need to know

Spec showdown

Which is the best? Surface Laptop vs. Spectre x360 vs. XPS 13

< >

Pre-order: Surface Laptop | NEW Surface Pro


Next week, Microsoft is set to patch a collection of security loopholes that have served as a major vulnerability within Internet Explorer. A few months ago, security firm FireEye, discovered that they could exploit machines by using a piece of code that was drilled up by hackers. A second security confirm, Websense, later confirmed the issue and now a patch is ready to be sent out this Tuesday.

More →

Preparing for the epic Titanfall launch, Microsoft has set out to release two different updates to their Xbox One console before the March 11 date arrives. The first patch went out this month, and introduced a few new features; along with a bug, we are calling “the black screen of (temporary) death”. The next update that will be coming in the first few days of March is being handed out to a select few individuals for early testing and one of those people could be you.

More →

Between the various sales, discounts and all around good word-of-mouth, the Dell Venue 8 Pro, featuring Windows 8 (x86) on an 8-inch tablet, has become a mini-hit this holiday season. In fact, we wouldn’t be surprised if many aren’t given out as Christmas gifts in two days.

One complaint about the otherwise stellar device is the ambient light sensor. Out of the box, the brightness on the Dell is very dim. That’s surprising if only because throwing it into manual control (instead of the default auto adjust), you’re treated to a very bright display—easily the brightest of the all the 8-inch Windows tablets on the market. The reason it’s so dim? To preserve battery life and rake up that 10 hour rating. Unfortunately, Dell’s settings are too aggressive.

Luckily, they seem to be listening. A new patch came out a few days ago, featuring new ambient light sensor settings, which will optimize them for better performance. The update is just 2 MB and it will only take you a few moments to install.

More →

If there's one area where have heard a lot of complaints on it's the WiFi function on Windows Phone.

The problem is a bit niche but it has frustrated quite a few of you ever since 2010. That "problem" is when the phone goes to the Lock screen, WiFi automatically disconnects. Obviously Microsoft had good intentions in mind here with power-saving as the chief concern. But recently, evidence and personal anecdotes seem to betray the idea that turning off WiFi (when not in use) saves battery.

More →

Getting updates on Windows Phone 7 so far has been a mixed bag for consumers. On the one end, they’re basically simple, universal OS patches in the form of CAB files, allowing even early prototype phones to keep upgrading, years after release.

On the other end, they’ve been just awful due to the lack of carrier support in actually rolling them out to end-users. The process is still much better than whatever Android has to offer but it still pales compared to the iPhone in many ways.

More →

Last week we reported WhatsApp had disappeared from view on the Windows Phone Marketplace (it was actually set to private), and were awaiting official clarification on the matter. Turns out, according to a report over at MonWindowsPhone, the app has a serious security flaw, which requires the team to pull the app and look into the problem. An update is well on its way.

The app enables Windows Phone owners to send messages to other devices and is available for multiple platforms. German website ComputerBild reported that an Android app, called WhatsAppSniffer, allowed users to access messages sent using WhatsApp on a WiFi network. The developers of the popular messaging service are patching the app due to it sending  messages via XMP protocol and in plain text.

We'll keep you posted and will announce when the app is available on the Marketplace with the patch bundled in an update for existing users. In the meantime, you can checkout some early images of the Windows Phone 8 version of WhatsApp.

Update: We've received word from a WhatsApp employee stating the following in an email,

"This has nothing to do with security. Please don't spread mis-information."

Take it as you will. We'll look forward to more information and possible clarification. Until then, WhatsApp is not available until the promised update is released to the Marketplace.

via: MonWindowsPhone

More →

Samsung Omnia 7 updates back on

Seems as though everything is back on after we mentioned the patch Samsung released yesturday for their Omnia 7, which addressed the issue with devices not being able to update. Microsoft have confirmed in a blog post that the Samsung Omnia 7 handsets will begin receiving either NoDo or 7392 (dependant on whichever stage you're at) in stages, but unfortunately no word has been said on the Focus.

If you haven't recevied any error on your Omnia 7 with updating to 7392 from NoDo (code: 801812C1) then you will not need to use the Samsung patch, just update as you usually would via Zune or Windows Phone 7 Connector. So, fantastic news all around, right? We'll keep you all up-to-date with anything we receive for Focus handsets.

Source: Microsoft

More →

Samsung release Omnia 7 patch

Samsung has just come out with a new patch for their Omnia 7 product to make updating to 7392 (or NoDo) a reality without fail - or so it seems. We're (as of now) unsure whether the Focus will receive a similar patch from the manufacturer, but at least this is a sign of progress behind the closed doors. Also, Microsoft has not yet given word on when Samsung devices will begin to receive the May update.

Since this patch is for devices that have failed to update to the May security build, we would recommend that everyone who hasn't actually attempted to update in the first place not to use this patch unless the update to build 7392 failed with the error: 801812C1.

Source: Samsung,via: WMPU, Monsmartphone

More →

And rounding up the dreaded SMS-2016 issue, whereby SMS messages come dated from the year 2016, is Palm with a nice patch for their CDMA Treo Pros on Sprint and Alltel.

The patch is a simple .cab file.  Just download, install and soft-reset and you should be good to go.

For those who want direct links to the .cabs, here you go.  Just click and download:

Or browse to Palm's support page for Sprint or Alltel for more information.

[Thanks, lunigma, for noticing!]


More →

Y'all remember that 2016-SMS timestamp bug we discussed a few weeks ago? The one that caused all incoming text messages to be dated from the year 2016?

Well, good news as HTC has released patches for Telus, US Cellular and Alltel users (Sprint got theirs last week; not a peep though from Verizon yet).



US Cellular

Remember, these don't play too well with custom ROMs, so best to stick with the 'Ziggy' patch.  

Sure, this was an unfortunate bug, but three to four weeks isn't too bad for an official patch, we suppose...we mean in comparison to where we were a few years ago (Anyone remember the Sprint 700wx SMS debacle? That was like a 6 month wait!)

[Thanks to Gregory P for the Telus tip!]

More →

Well, it's not a mighty re-flash of the whole ROM, nor does it bring any new features to the table and in fact, it actually looks kind of dangerous to apply (see below), but Samsung has released a radio firmware update to help with dropped calls on the Verizon Omnia II (see hands on video).

Yeah, not exactly thrilling, though we suppose if you have been experiencing poor call performance, you may want to look into this lil' patch.

Now the caveat: its a finicky update, meaning it official doesn't work on Windows 7, only XP. Going further, a few users have reported problems with "bricking" their phone during the update.  We don't want to be alarmist, but make sure you follow the directions exactly as described.  Oh, and if you run the update in compatibility mode in Win7, evidently that can work too.

Get the patch right here...if you dare!


More →

No phone is perfect, and the Sprint Treo Pro has some hiccups as well. One that has been documented by many is an issue with the ringer where essentially the settings get corrupted in the registry, resulting in "silent" incoming calls:

The root cause of the Treo Pro No Ringer issue is related to a rare corruption of the Treo Pro’s registry key. This can lead to the smart phone not ringing and causing the user to miss an incoming call.

If you see a Software Version that is T850EWW-1.04-SPT you should install this update.

Interestingly this "update" looks to be an old fix for the Treo 750 found here and brought to Palm's attention here, though a complete tear-down of the official .cab fix needs to be done to confirm.

This also does not address the other missed-call problem associated with fringe reception (documented and addressed here), that is the one where you get no notification at all about a missed call as opposed to just a silent ringer.

Get the official patch/update from Palm here.  For those on the go, here is the OTA update link. And remember that you'll have to re-apply the fix if you hard-reset your phone.


More →

Notification Fix for Epix Pops up

Got an Epix? Noticed that when the sucker is in standby/powersave mode, no matter what you do in the notifications settings, emails just won't make noise? It's not your fault. No no no, it's not your fault. It's not your fault.

Now that you've let that angst out, go on and grab the pdf explaining how to download the hotfix. Or really, just grab the cab file from here (hint: click the 'etc' link at the very bottom of the software tab). This direct cab link, but don't forget that since it's a cab and not a ROM patch, you're going to need to reinstall after a hard reset.

via pocketnow

More →

Palm Treo Pro Gets BT Bug Fix

If you have a Treo Pro you may be interested in this quicky patch from Palm:

If you are in an active call using bluetooth car kit or bluetooth headset and you receive a second incoming call and you let it ring or you ignore the incoming call, the call will be diverted to Voicemail. The first call remains active but you can no longer hear the caller (the caller can still hear you). The audio has been lost. If you answer the call and swap between calls or reject the call, the issue is not seen.

We have seen this bug reported in our forums for awhile and it's nice to see quick fix out there.

One word of caution: technically this is for the Vodafone/Euro version only, though we suppose it may work on the unlocked variety if you really, really need it. If not, we bet that'll be out lickity split.

More info here and a direct .cab download can be found here

Thanks marianne/roydok

More →

Ever have an e-mail you know you sent just seem to sit in your outbox?

Turns out you're not crazy. At least not because of this. Fellow WM Expert George Ponder has turned us on to a post over at Smartphone Thoughts that helps shed light on the whole thing.

It turns out there is a bug in Windows Mobile 6.1 that can keep messages in you outbox for good. It goes like this:

  • When you send an e-mail, your phone attempts to use the specified SMTP server name. (On my AT&T phone, it's, a holdover from the Cingular days.) Think of that as Mailman 1.
  • If Mailman 1 isn't available, for whatever reason — I like to think he's enjoying a tall cold one on the beach — Windows Mobile 6.1 looks for an alternate SMTP server. That'd be Mailman 2. But if there's no alternate server listed (has there every been?), and your phone can't connect with the first server (that beach/beer thing again), then that e-mail gets kicked into a perpetual outbox loop. Even when your phone reconnects later, that e-mail's still stuck, unsent.

The Microsoft readme file (read the entire thing after the jump) is a little more ominous:

This behavior is associated with a feature that is introduced in Windows Mobile 6.1. The feature allows for mobile operators to specify an alternate SMTP server name that is used if e-mail messages cannot be sent by using the user-specified SMTP server name. If the mobile operator does not specify an alternate SMTP server name and if the Windows Mobile 6.1-based device does not connect, the e-mail account is corrupted and cannot send e-mail messages.

How do we fix this? With a simple download. Hit up Microsoft's Windows Mobile 6.1 POP and IMAP Send Mail Patch page. You can either install from your desktop or directly onto your phone as a cab file. Your phone will immediately reset, and all will be right in the world. Note that if you hard-reset your phone, you'll probably have to re-apply this patch.

The bug applies to IMAP and POP mail, but not Exchange mail or SMS/MMS text messages, and it affects touchscreen and non-touchscreen phones. If all of this is Greek to you, go ahead and apply it.

Fair warning: Microsoft says anything that's stuck in your outbox will now be sent. So if you have any e-mails with the subjects "Honestly, it was just dinner," "Dear boss, screw you," or "I promise I'll have the money on Tuesday" in there, now would be a good time to clean them out.

Obligatory rant: Why have none of the wireless carriers made notice of this yet? (Edit: HTC just sent out a message on its Twitter feed a few minutes after we first posted this.) It's just one more disconnect in the strange relationship between the carriers and Microsoft. And for more about that, be sure to check out the latest WM Experts Podcast, in which Dieter and Malatesta dive deep into that dysfunctional family.

Windows Mobile 6.1 POP and IMAP Send Mail Patch

This behavior is associated with a feature that is introduced in Windows Mobile 6.1. The feature allows for mobile operators to specify an alternate SMTP server name that is used if e-mail messages cannot be sent by using the user-specified SMTP server name. If the mobile operator does not specify an alternate SMTP server name and if the Windows Mobile 6.1-based device does not connect, the e-mail account is corrupted and cannot send e-mail messages.


Follow all steps below completely and in order. Be sure to complete all steps.

Follow only one set of instructions below, depending on whether you synchronize your device to a PC:

  • If you connect your device directly to a PC with a USB cable or cradle, follow the instructions for Windows Mobile users who connect to a PC to synchronize.

  • If do not synchronize your device or phone with your PC or you only synchronize your phone or device wirelessly with a Microsoft Exchange Server or other e-mail and calendar systems, follow the instructions for Windows Mobile users who do not connect to their PCs to synchronize

Windows Mobile users who connect to a PC to synchronize

Download and run the Windows Mobile 6.1 POP and IMAP Send Mail Patch.

Check to make sure you have the latest version of ActiveSync or Windows Mobile Device Center:

ActiveSync 4.5 or Windows Mobile Device Center 6.1.

Connect your Windows Mobile device to your PC, download and then run the Windows Mobile 6.1 POP and IMAP Send Mail Patch for Windows Mobile

Windows Mobile users who do not connect to their PCs to synchronize

For users that do not connect to PCs, there is an update file (.CAB) available to make this update. (Note: There are a number of ways to install a .CAB file and below outlines a popular method).

Using the Microsoft Internet Explorer Mobile browser on your device, go to this location and download this file, WindowsMobile61-KB958639.msi, to your Windows Mobile device. This file will install the update directly on the device.

Installation Instruction:

From your device, navigate to the file you downloaded, and then tap it (or select the file and press “OK” button on a non-touch screen device) to install the update. If you are unable to download the file proceed to step 2.

If you are unable to access the file in step 1 on your device, open Windows Internet Explorer on your PC and click here to start the download process. After downloading the file, attach it to an e-mail and send it to an account you can access on your device (the send mail bug will not prevent you from receiving messages). On your device, open the e-mail and save the attached file; on some devices, you may need to synchronize your e-mail a second time to download the attached file. Then navigate to the file on your device and click on it to install the update.

Note: After you install this update, your device will automatically restart to ensure that the update is complete

Installation tips

Check the messages in your Outbox

More →

DST Patch, Part Deux

Apparently the first patch was buggy, in that its attempts to fix what hour is what actually broke what hour is what. All's well now, though. Go clickly and get your WM5 phone ready for the new times that are a-comin'.

These changes could cause clocks and Microsoft Outlook calendar appointments on Windows Mobile-powered devices to display incorrect times for March 11 – April 1, 2007 and October 28 – November 4, 2007 and again in subsequent years. You can find more information about the exact dates and potential impact in the Changes in DST section.

Read: Windows Mobile Updates for Daylight Saving Time, via Download Squad

More →