Is There A Facebook Messenger App For Windows 10
Joyce Buzard
I have strange issue with this app in MS Windows 10 after last days. I have installed standalone application and MS store app to, in both app I cant type text into message or sear field. This strange bug appear on standalone app before some week, now the same error is in MS store app too. This make this apps unusable
Same exact issue. I'm on Windows 11 latest. Started with the native app downloaded from messenger. com. It refuses ALL keyboard input in the app. I've tried everything. I uninstalled it and installed the Messenger app from the Microsoft Store and it was working fine for about a week, and now it is also not accepting any keyboard input.
Hope i was able to help. In bad case you have to do all the stuff, but i reccommend to first activate Tablet and Ink Support, if it maybe was deactivated by an update or one of the known "optimization tools",
maybe accidentaly by the user, because it tells you it is safe to deactivate. ( I also dit, SIGH! )
Hello! Yes i did many attempts to find the solution. It toome me almost 2-3 months. Other people just has read the last thing i did and made as his/her own solution. The Tablet and ink writing service seems to be the thing that needns to be acvive, even if you do not have a tablet pc.
Thanks!
Stopped working 6 months ago when they shoved the microsoft store version down our throats. The previous standalone was fine, but the MS store one relies on this service, apparently.
Oh, and, weirdly, you DO have to reboot, sadly. Tried without and did not work.
Take a look at the following website and follow steps there:
-us/account-billing/fix-problems-with-apps-from-microsoft-store-93ed0bcf-9c12-3df6-6dda-92ec5d0415ac
Run Windows Update and download and install all updates.
In the installer page of the application in the Microsoft Store , you shall see option to contact support and make sure report these issues.
You may open start and search for feedback and open the Feedback Hub app and report these issues.
With Facebook having stopped their first party (OSmeta-based and very bloated) applications for Windows 10 Mobile months ago, users have had to look elsewhere for their fix of family news and jokes. So what options are still working and what about Facebook Messanger and Instagram (also now part of Facebook's empire)? I investigate, in this last feature before Christmas. (AAWP will be back on December 27th.)
Messenger is particularly important for many people, especially for intra-family communication - I've lost count of the number of times a member has said 'Did you not get my message?' and it turned out they'd got confused and sent it by Facebook Messenger rather than Messages or iMessage (or whatever). So it does perhaps pay to keep an eye on Facebook messenger too, even if you're not a heavy user!
Instagram is totally separate, mind you, effectively a fairly recent Facebook acquisition. In theory, there's the excellent third party Winsta UWP, though it's currently a bit unstable and I'll report more on that in the Flow columns here on AAWP. Plus there's a new Instagram PWA incoming from Facebook, which will hopefully work as well as the one Twitter put up online and in the Store. Update: good news and bad news. It's now available for all Windows 10 devices and even installs on W10M, but it doesn't actually run and connect up. Oops.
By the way, you may have thought I was kidding about the bloat of Facebook's old first party clients for Windows 10 Mobile, but I'm not. The 'Facebook' app in the Store was a whopping 168MB and took about 15 seconds to launch on a Lumia 950. Which is ridiculous. And good riddance.
But Facebook does have its uses. It's still loved by non-techy relatives, typically - we all have a cousin or grandparent who will only use it and it's our lifeline to what they're up to. For this reason, and also because lots of lesser web sites let you 'log in with Facebook', saving you having to make accounts for everything, I'd advise not leaving Facebook altogether.
Which leaves the issue of how to access Facebook in 2020, especially under Windows 10 Mobile. Happily, Facebook has to provide a low bandwidth way into its content via the Web and this can be used, either directly, or via a number of 'web-scraping' applications.
In fact, you can get just a bit more screen real estate and convenience by turning the URL into an 'app' yourself with PAWA or just pin it 'as is' on your Start screen. Or just add it as a 'Favourite'. It's up to you.
In Edge, go into '...' and Settings and then pick 'Desktop version'. Note in particular that you're still going to m.facebook.com, but it's being interpreted in slightly more sophisticated fashion because Facebook's server knows that you're using something (in theory) higher end. So you then get:
Facebook Messenger needs addressing next, since sending and receiving messages is all handled in the interface here, whether you're looking at the ultra-basic or DMH mode. There's no notification support outside of Edge, mind you, so it really isn't a good idea if people try to contact you urgently in Facebook Messenger and you're using Windows 10 Mobile!
Well, with one major caveat. The DMH mode has a javascript glitch (either at Facebook's end or in Edge locally, it's not clear, but it certainly hasn't been tested in this combination)! So, when you send a new message/reply, it doesn't appear in the message list, even though it has been sent. Worse, when the other person replies, you don't see that either! See the comments in the screenshot above!
You're forced to refresh the page to check, or - easier - just move away from this Facebook pane/tab and then move back to load it again. This is a pain because, apart from this glitch, this DMH mode works really well for Facebook on the go under Windows 10 Mobile. It's not a showstopping bug but... it is a nuisance.
Now, if the DMH panes look familiar, it's because they're the basis for what I'm calling DMH+ applications. LightSocial Pro is one such, featured here, though SlimSocial and Likebook for Facebook do a very similar job (though their 'Messenger' presentation isn't quite as neat IMHO). In each case, the application presents itself to Facebook as a Desktop browser going to m.facebook.com and then the HTML returned is subtly modified, perhaps setting the background dark (to save power), perhaps media detecting and local saving are made possible, you get the idea. As I say, I'm calling this DMH+. Here's a brief walkthrough using LightSocial Pro:
Two main - and related - approaches then, each more satisfactory than you might think overall (not least in terms of not having to endure the original bloated Facebook code) but each flawed in terms of Facebook Messenger operation. It would be nice if Facebook opened up its APIs to allow third party clients, but I'm not holding my breath. Plus it's late in the day for UWP apps for Windows 10 Mobile now...
Oh, as noted in the comments below, there's also 'Messenger for UWP', which takes the glitchy Facebook Messenger web view data above and puts a complete new UI/skin on it, along with detecting new messages and throwing up Windows 10 notifications:
What's not to love about this? Well... it's slow to start, slow to work, produces duplicate notifications, and is impossibly hard to navigate in terms of finding anybody, in my experience, with notifications not actually directing you to the appropriate chat. Maybe the developer can leap in with a major update here?
MSN Messenger (also known colloquially simply as MSN[2][3]), later rebranded as Windows Live Messenger, was a cross-platform instant-messaging client developed by Microsoft.[4] It connected to the now-discontinued Microsoft Messenger service and, in later versions, was compatible with Yahoo! Messenger and Facebook Messenger. The service was discontinued in 2013 and was replaced by Skype.
The client was first released as MSN Messenger Service on July 22, 1999, and was marketed under the MSN brand until 2005, when it was rebranded under the Windows Live name. It has since been officially known by the latter name, although its first name remained in common use.[5][6] In June 2009, Microsoft reported the service attracted over 330 million active users each month, placing it among the most widely used instant-messaging clients in the world.[7]
In 2018, a free version of Microsoft Teams became available after years as a component of an Office 365 subscription. Teams inherited the Microsoft accounts architecture, allowing users to invite contacts from the discontinued services, MSN Messenger and Skype.
Before the product was renamed Windows Live Messenger, it was named "MSN Messenger" from 1999 to 2006. During that time, Microsoft released seven major versions as follows.The first version of MSN Messenger Service, version 1.0 (1.0.0863), was released July 22, 1999. It included only basic features, such as plain text messaging and a simplistic contact list.[8] When it was first released, it featured support for access to America Online's AIM network. America Online continually tried to block Microsoft from having access to their service until eventually the feature was removed, and it has not re-surfaced in any later versions of the software.[9] AOL did this by exploiting a buffer overflow bug in AIM, which causes it to execute a bit of machine code sent by the server. When this code runs, it determines if the client is AIM and sends a message back to verify the client.[10] Since then, the software has only allowed connections to its own service, requiring a Windows Live ID (.NET Passport at that time) account to connect.Microsoft released the first major update, version 2.0 (2.0.0083), on November 16, 1999. It included a rotating advertising banner and the ability to customize the appearance of the chat window. It came as an install option for Windows Me. This version was followed the next year by version 3.0 (3.0.0080), which was released May 29, 2000. It included file transfers and PC-to-PC and PC-to-phone audio capabilities with Net2Phone and Callserve,[11] two of the larger VoIP providers.[12]
d3342ee215