Whatsapp En Windows
Hildegard Mccauley
The bizzare thing that happened is that, even after I closed Whatsapp (it was not visible anymore neither on the task bar nor on the tray icon area), Whatsapp kept running on the background and displaying notifications of new messages arriving on my whatsapp on the screen!
How can I force Whatsapp to be closed completely when I close it? Certainly that raises the concern of how many other apps are running on the background after being closed? I'm talking here, obviously, of explicit apps that should work only when opened by the user and displayed on the screen. I'm not talking about normal background processes of apps used to improve performance.
A background process to optimize performance is completely different of an app fully running and receiving messages after being closed. It's like closing Outlook Email and keep receiving notifications that a new Email arrived even though the app was closed. That didn't happen with outlook. but it's a good analogy. That behaviour from Whatsapp is unacceptable!
Settings>Apps>Installed apps>"scroll down to whatsapp">"click on 3 dots">Advanced options>Back ground apps permissions> "take your pick from always, optimised, and never. Probably 'never' in your case">Runs at log in>"you can toggle this on/off if you do/don't want it to automatically kick off at start"
@NeetuKahlon I would say you told me everything I needed to know, but the only issue here is that "never" was already selected for background permission for Whatsapp. I'm certain I didn't follow this path suggested by you before, so if I changed that background behaviour, it was done by other means. Anyway, I appreciate your help and believe that to be the solution. If I keep seeing notifications when I close Whatsapp, I'll let you guys know. I just need to enable Whatsapp notifications again in Windows.
You're absolutely right, that WhatsApp behavior is frustrating! It seems like WhatsApp for Windows 11 isn't truly closing when you hit the "X" button. Don't worry, there are ways to take control. Here's what's likely happening and how to fix it:
Many apps, including WhatsApp, use background processes to stay connected and receive notifications even when the main window is closed. This can be helpful for staying up-to-date, but in your case, it's clearly overstaying its welcome.
1. **Task Manager:** Right-click on your taskbar and select "Task Manager." Find WhatsApp in the "Processes" tab and right-click it, then choose "End task." This will forcefully close WhatsApp and all its background processes.
2. **Background App Settings:** A more permanent solution is to adjust WhatsApp's background settings. Go to Windows Settings > Apps > Installed apps. Find WhatsApp, click on "Advanced options," and under "Background apps," choose "Never." This will prevent WhatsApp from running background processes altogether, ensuring it truly closes when you hit the "X" button.
By following these steps, you can regain control and ensure WhatsApp behaves like other apps, closing completely when you close the window. Remember to check these settings for other apps you suspect might be lingering in the background as well. You deserve to be in control of what runs on your system! Simply don't use apps like NsWhatsapp APK.
Yes, I have. The program window closes, but when you check the running processes, Whatsapp is still running. And if someone sends a message, it pops up... that is intentional I suppose, but an option to actually shut it all down is missing.
While that works with every other program, whatsapp desktop does not close completely with that shortcut, it only closes the window, four other processes stay open. It does however close as expected, if I do File -> Quit.
No, that's definitely not a client bug. It sounds like bad behavior of the window manager - whether or not it is a WM "bug" depends on whether the WM authors intended for it to be so badly behaved or not.
WMs generally use the Mod4 (aka "Windows" or "Super" button) for bindings. Occasionally some other modifiers are bound by the WM, but binding Ctrl-anything sounds like a bad idea for a WM. Most clients expect to be able to handle Ctrl-key combinations themselves.
As far as I understand from my own programming with Qt, a "close event" should implement whatever is necessary to do when the window (through whatever means) is closed. And my assumption here is, that whatsapp-desktop doesn't have this implemented.
I don't disagree regarding quitting and closing not being the same. But I don't have Ctrl+Q mapped to "terminate application", but to "close window", which is exactly the same as mapping Alt+F4 to that event.
Graphical "applications" are "clients" to the "display server". What a client does if you close one of its windows is completely up to the client and its implementation. Apparently WhatsApp follows an SDI model and therefore does not terminate if you close one of its windows. That this has not happened with random other clients you've been using in the past is meaningless.
I agree and understand this. And it was also my assumption; after all, whatsapp-desktop may have been designed to stay open without a window, so that messages can be received even when the user decided he just doesn't want the window open.
There are many de-facto standards. `Ctrl-Q` is a common key for quitting a program. This is both reflected by and reinforced by some toolkits (e.g. Qt) using it as a default for many applications. If you write a Qt program, you certainly can chose not to use Ctrl-Q for "quit", you could use Ctrl-H if you wanted, or Ctrl-Shift-Space-F3-Y if you want to appeal to emacs users But Ctrl-Q is a de-facto standard client / application bound key. This is why it is a bad idea for a window manager to bind that key as it will result in clients never detecting the key press.
For very similar reasons, clients (i.e. applications) generally do not bind Mod4 key combinations. There certainly are exceptions, but it is generally expected that Mod4 key combinations are for WMs and Ctrl key combinations are for clients (as are most Alt/Shift combinations unless they are paired with Mod4).
So, in short, you certianly may use a non-convential key binding scheme for your WM. But if you do, you really can't expect all programs to behave nicely with it. The fact that some do is just dumb luck.
Using the mod4 key (usually the "Windows" key if I understand correctly) for WM key bindings is certainly the way to go. As a matter of fact, I have set up most of the Enlightenment keybindings with the mod4 key. So if I want to stick with 'Q', I should probably configure mod4+Q to close windows.
I realized today that whatsapp-desktop actually stays open if you close the window via its "X" from the window, as in the X icon of the window bar. So this just confirms that the idea of the whatsapp-desktop developers was to keep whatsapp running in the background, so that you can receive messages even if the window is closed.
Is it correct then, that the XDestroyWindow event is actually the same as clicking the X in the window title bar? If so... then isn't it true that by binding Ctrl+Q to XDestroyWindow only has the disadvantage that any client's Ctrl+Q key mappings are not being triggered? I mean... after all, all I am trying to do is close a window with a shortcut rather than having to use the mouse and click that X in the window title bar.
Yes. And this is precisely the problem you are concerned about in this thread. Ctrl-Q when bound by the client generally means "quit", and you've stated that when you use Whatsapp's Quit menu entry it does indeed fully shut down.
I do want a window to close, not quit an application... for example, when using firefox, the Quit command from the file menu (or the shortcut Ctrl+Q, if it wasn't reconfigured as in my case), would close all firefox windows, e.g. quit firefox entirely. That is not what I would want. I may have two firefox windows open, but just want to close one of those windows.
Open WhatsApp on your phone, tap on Menu, then WhatsApp Web. That will show you all your WhatsApp web active sessions with last active time. All you need to do is to tap on Log out from all computer. That will logout from all the active sessions of your WhatsApp web from all the devices you were logged in.
Endpoint is blocking Web. WhatsApp on a single user although all users seem to be running it fine and I have added an exception of web.whatsApp in chats categories and called it in Policies settings. Web WhatsApp page loads correctly but after QR scan it gets stuck at Loading your chats. Getting below error:
Based on the error you've shared on the phone and Central. It seems like there's a User base policy applied to the said user account.
You may need to validate your current web control policy and check if you have userbase policy active on your policy setting. If you do? Then you may remove this user account for this user to access the website.
Can you share some more details. Basically the policy is being applied on user level and device level. I have tried to remove policy being applied at user level but still no success. users/ devices connected to this same web policy are able to use web.whatsapp without any issue but on this particular user after allowing web.whatsapp. Whatsapp page opens and after scanning QR code doesn't show the chats screen and get stuck on loading chats.
c80f0f1006