GoodBytes

Hibernation needs to be enabled

WSL2 is what we use in our development workflow. 0 issue, it's been real solid. We use Ubuntu LTS on it (gets updated over time). Everything we throw at it works perfectly. Out of the box GUI support requires Win11, else you'll need to use a X11 Display Server under Windows. Many popular IDEs for development have WSL integration support for a seamless experience and best performance. It's also best to keep all project files under WSL2 environment for best performance. Use Windows Terminal: https://apps.microsoft.com/detail/9n0dx20hk701 (built-in and default under Win11) It's a modern terminal that supports everything, which the old Command Prompt just doesn't as it was never really updated since the early days of Windows 10 to make it usable... but only that. It needed to be reworked from the ground up, and that is what Windows Terminal is. It opretty much supports everything you expect. Unicode, Emoticons, all types of fonts, font smoothing, panes, tabs, links, and lots more. It is nicely customizable as well.

We don't know, but I think WSA will remain, but Amazon Store won't be there. At worst, we can probably push in a Pixel phone OS with the latest Android version to WSA to get a newer version of WSA version of Android. Like what you need to do to get Google Store Service support, as MS can't provide it, due to Google.

The biggest issue is the lack of Google Play Store support (not Microsoft fault). The problem is that even if you sideload apps, due to the deep integration of Google Play Store that apps have with it, most apps just crash when you do certain things, or just don't even start (crash at launch). The only thing one can do is side load a modified Pixel firmware where Google Play Store has been injected inside, and that means that Amazon isn't getting money from app sales (the little that already get), and that means that Amazon isn't interested anymore in supporting WSA. So many Android apps are deeply tied to Google Play Store, and that is the big problem. Only the ones on Amazon App Stores (the very few they are), are coded in a way to support both APIs. Remember that Google Play Store is more than just the Store. They are Google Maps, Tools for Google Apps for telemetry, in-app purchases, Ads, and more. If any app uses any of these things (most does) and has no alternative behavior beside expecting that the device supports Google Play (which is most cases), then the app will just not run.

Windows 11 has Android emulator. But out of the box, it doesn't support Google Services. They are guides online to use the image of a Pixel phone to have Google Play service

Sounds like you don't have the latest version of WSL. It should be fetched from the Store app. OR, this is the first distro that you are installing on the system and so: --import-in-place should be used. wsl --import-in-place Kali "C:\wsl\kali-linux\ext4.vhdx"

As per documentation: wsl --import Kali --vhd "C:\wsl\kali-linux\ext4.vhdx" --version 2

Just to be sure I understand you. Where did you place your files? Under WSL or outside WSL? WSL2 (I'll focus on "v2" of WSL), can be seen as a fancy VM (specialized for Linux based OSs) where it has deep ties with the OS, allowing you to cross both Linux based OS world and Windows. That said, it is still a VM. If you have files IN WSL2 environment, you can access them through File Explorer, by clicking on the "Linux" item on the navigation bar. If you don't have it, then you are probably under Windows 10. Under which case, you can type "explorer.exe ." (notice the space and the "." after "explorer.exe") under your WSL2 environment, and you'll open File Explorer exactly at that location. It should be a network location. WSL2, as mentioned, is really a VM at the end of the day, that means it has a VHD of some kind. It means that you can export it and import the envirement. This avoids reinstalling/reconfiguring everything. You can use these commands which you execute under Windows (Command Prompt or PowerShell) to do this: https://learn.microsoft.com/en-us/windows/wsl/basic-commands If your files are outside of WSL2 envirement, meaning not under your Linux based distro env, then you can just treat them as any files of your system. The other system WSL envirement will see them just fine. You can view your Windows files under Linux via /mnt/ folder, where you'll have, your drive letters. So, if your files are under Documents, assuming a starts Windows install, it can be accessed via: /mnt/c/Users/<account name>/Documents

WSL can see all Windows files.

You can opt-out of the Insider program via Settings panel. However, the build will expire soon (See Windows About panel to know expiry date). Unless your built that you have is match the official build (a small window), a clean install would be required to get the official non-short-expiry build.

Contact MS support. Start the "Get Help" app. It has been reported that MS is having activation server issues recently when people do BIOS updates, despite using a MS linked account. Basically, it sees the system as a new one. It just needs to be corrected.

They are 3 ways to do this for Windows 10 Create a local account and don't enter a password when asked. For Windows 10/11 and that is to use a MS linked account, and use Windows Hello facial recognition (this is more for laptops, or desktops with a compatible webcam like the Logitech BRIO 4K camera) This one works with Windows 11 as well, and that is to use a MS linked account as normal and use Microsoft's very own utility called "Autologon" to auto-login for you: https://learn.microsoft.com/en-us/sysinternals/downloads/autologon. The utility doesn't need to be installed or running on the back once setup. It simply configures Windows hidden account part to basically starts with your password entered in the field, and auto login for you the moment it gets to the login screen (everything is encrypted, but not a strong encryption and can be retrieved if someone has physical access to the system. Best to use for a home desktop computer. Use Windows Hello for laptops, in the case the laptop is stolen). Your experience will look very similarly as if you had no password on the system when you start it up.

Windows 11 requires and is designed for and optimized for: SSDs and eMMC storage (well not technically, but other disk performance requirements force SSDs or eMMC storage, unless some crazy HDD technology comes out, it's a non-HDD you must use to comply with Windows 11 system requirement). Hence why you no longer have any laptops on the market running Windows 11 with an HDD as main drive. Your drive is probably fragmented, or you have network drive/folder shortcut/link somewhere.

Short answer: Edge is Chrome but uses MS services over Googles, consumes a bit less memory and easier on laptop in terms of battery life, has improved touch controls, oh and it has all the needed codecs to play nice with all streaming services, including support for 4K HDR Netflix content, which Google refuses to implement. It also brings some nice unique features, like collection (tab grouping), and easy access via a side panel to Bing Chat (ChatGPT 4 with full online access). Everything can be disabled in the settings panel if you don't care. Edge web browser is packed with options (maybe a bit too much these days). I other words, Chrome with Microsoft touch (good and bad). Google pretty much doesn't care about Chrome, always playing catchup to Edge, or just enjoys the advancements that Microsoft makes to Chromium (where all web browsers using Chromium benefits); Microsoft pushes new features in Edge. I seriously don't see a reason to use Chrome over Edge, beside one preferring Google privacy policy over Microsoft ones (personal preference thing). But yes, under Windows, since Windows 10, everything from Windows will use Edge, even if your default web browser is set to something else. So, search will use Edge. What you are seeing is Edge first time setup screen. I agree there should be "x" and not be full screen like so. I get they want user attention, and the user to take time to read things through and not go "Quick Close! Because I see something unusual". But that is still not a good reason.

Correct, these are sources. Bing Chat (aka: CoPilot) says what links are ads.

Your system is Windows 11 ready. You should upgrade to Windows 11 for the new context menu, which asynchronously load applications items to it, instead of synchronously. In other words, it shows the menu with "Loading..." on the menu items which takes time to load. And not to wait for Windows to load each item one at a time, until everything is loaded and then shows the menu. If one is stuck somewhere due to a bug, or just slow to do what it needs to do, you'll need to wait like you are experiencing now. So, yes, people complained about Win11 context menu, because their favorite apps feature lazy devs who don't want to upgrade. Now it is less and less an issue, as communities are pushing and devs are forced to add support.

This thread is old, but I'll speak for everyone and future readers: Windows 11 will install fine with workarounds, and will run fine with Win10 drivers. But performance is likely to be decreased mainly due to the CPU security features it wants to use, which the CPU doesn't support, and so has to emulate the whole thing. In addition, expect to do a clean install or in place upgrade manually at every release of Windows 11, as Windows Update won't be happy, due to the unsupported hardware. Windows 10 is supported until end (Oct) 2025, assuming no extensions is done. It's fine choice. Using a standard distro of Linux won't necessarily be lighter or lighter enough to see a performance gain. Windows 10 and up is all optimized for SSDs. Microsoft doesn't care about HDDs, and in addition Windows 11 has a requirement for OEMs an SSD, hence no more laptop with the infamous 1TB 5200RPM drive that they loved to put in.

Factually incorrect. Office is easier to use than LibreOffce/OpenOffice. The UI that Microsoft built and perfected is back by research, and still stands strong today for Office. Small buttons and menus with sub-menus isn't the solution. Heck, when the ribbon bar was first introduced, people mentioned several "new" Office features that already existed in past versions. Highlighting it's successfulness, despite a vocal minority claiming otherwise. Office uses open format, and support ODF as well. LibreOffce still has trouble with docx file format. Attempts to switch by companies and governments was attempted, and only been a disaster and quickly rolled back to Office. While LibreOffce has evolved a lot since many years, it still ages behind Office suit basic apps (Word, Excel and PowerPoint) Thinking that the average users are all idiots who only uses Bold/Italic/Underline in a word processor is foolish, not to mention completely outdated thaught. Linux based OSs, isn't always the best solution. Usability on a desktop front still lacks behind Windows, has no backup and restore solutions, no update fallback system, and many more things. In addition, you not only need drivers for every part of your system, but sometimes even software to get everything working especially on laptops. And on top of that, you need well developed drivers. Battery life and performance could be worse if proper support isn't there.

Windows 11 support WSL2 with GUI support (WSLg), Windows 10, does not. Don't forget to install your GPU drivers for ML under WSL2 Windows 11 has Windows Terminal as default command interface, Windows 10 does not, and needs to be specifically used. Windows 11 animation should not be slow. Please install Windows natively on your PC, and ensure every driver is installed. Windows 11 feature WSL2 as default and is ready to go. Windows 10 involves an extra step, as WSL1 won't cut it. Tip for WSL2: keep everything under Linux world in terms of projects files, to maximize performance.

You need Windows 11. It tracks and restores everything.

Everything points to the fact that you have malware on your system.

Dark is supported if the dev support it. Simple as that. You'll need to talk to the software company if it doesn't support it.

A properly configured system, including a proper and full implementation of UEFI. You should get 5-7sec from shutdown state (not restart). In other words, this: Or go to your local computer electronic store and test a system there, and you'll get a similar experience with Windows 11 (assuming decent hardware model is being looked at). Sadly, beside ASRock with its "Ultra Fast" mode, all other DIY motherboard put fake POST delays (even if you see the option and set it to 0sec), so that you can go in the UEFI by hitting the delete key. Normally, you can't. You'll need to go through Windows (or whatever properly UEFI supported OS) or physical button on the motherboard, if you have one. Also, AMD based system takes longer to boot if you are RAM isn't set to JEDEC speeds (In other words, not using D.O.C.P or EXPO I/II). This is an AMD issue that they never managed to really figure out, like Intel did. It did get better with the latest AMD CPUs with the latest BIOS release, but it's not Intel speeds. If your system has a dedicated GPU, it also needs to wait for the GPU to boot. This will depend on the graphics card, and on the graphic card manufacture vBIOS. Considering that none of them care, as no reviewers check for this, you get what you get. Intel iGPU's has the fastest boot time. So, all to say, unless you are buying an OEM system from large company (Dell, Acer, HP, etc.), decent spec'ed device, Intel based, with Intel iGPU, you won't get such speed shown in the videos, or an ASRock board with POST delay set to 0sec, and "Ultra Fast" boot enabled, Intel based system with Intel iGPU.

I am assuming you are seeing this screen, or something similar: The issue: Windows setup cannot find your SSD/HDD. Assuming that the drive is indeed detected by your BIOS/UEFI, it means that Windows Setup doesn't know how to interact with the SATA controller driver to communicate with your drive to give it commands to... well... put files on it. Windows Setup has built-in drivers for a wide variety of common hardware. The solution: You'll need to get your SATA controller driver on a USB flash drive, "Load Driver" or "Browse" (depending on the screen you are in) and select the driver. Windows Setup will load it and should detect your drive now. Please note: Your SATA controller driver CANNOT be in a .zip file or .exe (executable) or .msi (Microsoft Installer Package). It has to be an .inf (script file). This is because Windows isn't installed at this stage, and so it cannot interact with such files. It doesn't have the needed software or foundations to run beside what it needs to do its job.

Yea so it looks like your UEFI is missed configured. Make sure your BIOS is updated and set the options mentioned. Please note that if CSM was set to Enabled, then your UEFI emulates the legacy BIOS, for old OSs. That means that the main drive was formatted as MBR instead of GPT. This means that your system won't boot, because UEFI can only work with drive formatted as GPT, and legacy BIOS works with MBR only. There is a guide here on how to to convert the drive from MBR to GPT via a Windows built-in utility that Microsoft included in Windows 10.