No Metro = Windows 7 SP 2. Don't like Metro, stick with Windows 7.


Recommended Posts

Metro UI is ugly, keep that garbage for systems with touchscreens but spare the PC at least. Microsoft thinks that their WP7 UI would be fine on a Desktop but who needs touchscreen features on a system with a Mouse and Keyboard. No wonder why Windows 8 will be dead on arrival.

Metro isn't just touchscreen. And I guarantee you in 20 years, we won't be using mice anymore.

there are too many other great improvements made to just ignore Windows 8

I don't know about 'great improvements'. Personally, if Windows 8 was free, I'd actually prefer it to Windows 7 and just ignore Metro style apps. But I don't see a headline feature that would make W8 sans Metro worth the (probable) admission price. Unless you reboot your PC all the time or have a need for features like Storage Spaces, I wouldn't expect to see the big difference in day to day usage. Task manager improvements are nice to have but don't really get me excited about a new OS. While the explorer UI is changed it's debatable how much of an improvement has been made. As for the rest, I see quite a few niche features that are, again, nice to have but can't sell a whole OS. In that regard, I guess, I agree with the OP. For better or worse, Windows 8 is all about Metro.

I don't know about 'great improvements'. Personally, if Windows 8 was free, I'd actually prefer it to Windows 7 and just ignore Metro style apps. But I don't see a headline feature that would make W8 sans Metro worth the (probable) admission price. Unless you reboot your PC all the time or have a need for features like Storage Spaces, I wouldn't expect to see the big difference in day to day usage. Task manager improvements are nice to have but don't really get me excited about a new OS. While the explorer UI is changed it's debatable how much of an improvement has been made. As for the rest, I see quite a few niche features that are, again, nice to have but can't sell a whole OS. In that regard, I guess, I agree with the OP. For better or worse, Windows 8 is all about Metro.

I think vast majority of computer users get the OS preinstalled when the purchase a computer. Very few people comparable buy standalone os. Windows 8 is all about getting People consumers to buy a PC. I think the majority of PC sold in 4 years will be hybrid PC with Windows 8 installed.

Metro isn't just touchscreen. And I guarantee you in 20 years, we won't be using mice anymore.

I don't think so. Touch and even Kinect technologies won't replace the mouse anytime soon. But hey, in 20 years, maybe we'll have another way to interact with the PC, one that anyone hasn't even imagined yet, so who knows.

If your using Windows 7 your just using Vista with minor modifications.

For example, I wouldn't say that the taskbar change from Vista to Windows 7 is minor. There are many improvements, and new details and changes all over the place, all of which you can't fit in a Service Pack.

Which brings me to my original post. Windows 8 has even more improvements and changes than the jump from Windows Vista to 7, but when you take Metro out of the equation, then the improvements aren't really that many, you can fit them in a Service Pack.

Without Metro, the difference from Windows 7 to 8 just isn't as significant as the difference from Vista to 7, which is my original argument. Metro is already deeply integrated in Windows 8, make that optional or take that out, and you have changes similar to a Service Pack. That's why taking Metro out of Windows 8 as we have it today is irrational.

Thats exactly what people are going to do...by sticking with Windows 7 or jumping ship to Mac

A lot of you aren't giving Metro a time to mature. I think by Windows 9, there will be greater acceptance towards Microsoft goals with it. We're moving towards a future where computing will be more dynamic, and fits to your life, where as right now, we're stuck with bland, static UI's, where you have to point and click everything.

If you want to keep pointing and clicking around, that's fine, but personally, I'm looking forward to having a more fluid, and dynamic UI, that I can change to fit my needs. You can't do that with Windows 9x, XP, or 7.

When I boot 8 I see metro, something I don't need, don't have any use for, is ugly and completely useless to me, that means it is in my way and I need to get it out of my way by going to the regular desktop before getting anything accomplished.

Basically, because you see the StartScreen *at all*, it's a distraction. (Never mind that it's a waypoint, and is far less obvious than the Start menu it replaces.)

Then answer me this - why wasn't the Start menu (in XP/Vista/7) a distraction?

I run very few WinRT applications OR games (for any filetype for which there are both traditional and WinRT options, I go traditional - not WinRT; generally because the traditional application suits my needs better). Will this continue to be the case? No idea - the jury has not yet realistically begun deliberations, as the OS has not yet released. However, for that very reason, I can't dismiss WinRT out of hand.

Without Metro, the difference from Windows 7 to 8 just isn't as significant as the difference from Vista to 7, which is my original argument. Metro is already deeply integrated in Windows 8, make that optional or take that out, and you have changes similar to a Service Pack. That's why taking Metro out of Windows 8 as we have it today is irrational.

Taking Metro out of Windows 8, and there's still enough new and changed in it to warrant it not being called a service pack. Service packs were intended as a roll-up collection of security and fix bugs or minor tweaks, not to add hosts of entirely new features and large performance improvements each time - and bar WinXP SP2 that's what they've mostly done.

Windows 8 has a lot of rather large changes to the Windows kernel itself, and whether it's improved shutdown and and bootup speeds thanks to the default partial hibernation, Windows to go, Refresh & Reset, improved multi monitor support, WDDM 1.2, ISO mounting, USB 3.0, etc etc

Only a couple of those would even be normal for a service pack, maybe USB 3.0 and ISO mounting at a stretch .

Taking Metro out of Windows 8, and there's still enough new and changed in it to warrant it not being called a service pack. Service packs were intended as a roll-up collection of security and fix bugs or minor tweaks, not to add hosts of entirely new features and large performance improvements each time - and bar WinXP SP2 that's what they've mostly done.

Windows 8 has a lot of rather large changes to the Windows kernel itself, and whether it's improved shutdown and and bootup speeds thanks to the default partial hibernation, Windows to go, Refresh & Reset, improved multi monitor support, WDDM 1.2, ISO mounting, USB 3.0, etc etc

Only a couple of those would even be normal for a service pack, maybe USB 3.0 and ISO mounting at a stretch .

You seem to be forgetting Vista SP1: http://technet.micro...8(v=ws.10).aspx and Vista SP2: http://technet.micro...036.aspx?ppud=4

Let's compare the features you mentioned of Windows 8, with the features Service Packs added to Windows Vista:

Windows 8 USB 3.0 ------- SP1 Adds support for SD Advanced DMA (ADMA) on compliant SD standard host controllers. This new transfer mechanism, which is expected to be supported in SD controllers soon, will improve transfer performance and decrease CPU utilization. | SP2 integrates the Windows Vista Feature Pack for Wireless, which contains support for Bluetooth v2.1 and Windows Connect Now (WCN) Wi-Fi Configuration.

Windows 8 improved boot and shutdown ------------- Lot's of improvements in SP1 - SP2 improves performance for Wi-Fi connections after resuming from sleep. | S

P2 includes updates to the RSS feeds sidebar for improved performance and responsiveness. |

SP2 provides an improved power management (both on the server and the desktop), which includes the ability to manage these settings via Group Policy

Windows 8 ISO Mounting ------- SP1 Adds support for creating a single DVD media that boots on PCs with either BIOS or EFI. / SP2 includes ability to record data to Blu-Ray Disc media.

Windows 8 WDDM 1.2 --------- SP1 Adds support for Direct3D? 10.1, an update to Direct3D 10 that extends the API to support new hardware features, enabling 3D application and game developers to make more complete and efficient use of the upcoming generations of graphics hardware. | SP2 adds support for the 64-bit central processing unit (CPU) from VIA Technologies, which adds the ID and vendor strings for the new VIA 64-bit CPU.

Windows 2 Go in Windows 8 Enterprise -------- SP2 provides the Hyper-V virtualization environment as a fully integrated feature of Windows Server 2008, including one free instance with Windows Server 2008 Standard, four free instances with Windows Server 2008 Enterprise and an unlimited number of free instances with Windows Server 2008 Datacenter.

Windows 8 Refresh & Reset Metro based UI. Take Metro out, also take those features out. Still, let's compare --------- SP1 Adds support for new UEFI (Unified Extensible Firmware Interface) industry standard PC firmware for 64-bit systems with functional parity with legacy BIOS firmware, which allows Windows Vista SP1 to install to GPT format disks, boot and resume from hibernate using UEFI firmware. | SP1 Adds support for x64 EFI network boot.

And a whole other changes that you can check out on the links.

So take out Metro and all Metro related funcionality out of the equation. Are you still going to say that Service Packs don't add that many features and improvements?

Are you still going to say that Service Packs don't add that many features and improvements?

yes, because they usually don't add features, xp sp3 and vista sp2 are exceptions to that, it's very unlikely that Microsoft will port any of those features over to Windows 7 in a service pack

You seem to be forgetting Vista SP1: http://technet.micro...8(v=ws.10).aspx and Vista SP2: http://technet.micro...036.aspx?ppud=4

Let's compare the features you mentioned of Windows 8, with the features Service Packs added to Windows Vista:

Windows 8 USB 3.0 ------- SP1 Adds support for SD Advanced DMA (ADMA) on compliant SD standard host controllers. This new transfer mechanism, which is expected to be supported in SD controllers soon, will improve transfer performance and decrease CPU utilization. | SP2 integrates the Windows Vista Feature Pack for Wireless, which contains support for Bluetooth v2.1 and Windows Connect Now (WCN) Wi-Fi Configuration.

Windows 8 improved boot and shutdown ------------- Lot's of improvements in SP1 - SP2 improves performance for Wi-Fi connections after resuming from sleep. | S

P2 includes updates to the RSS feeds sidebar for improved performance and responsiveness. |

SP2 provides an improved power management (both on the server and the desktop), which includes the ability to manage these settings via Group Policy

Windows 8 ISO Mounting ------- SP1 Adds support for creating a single DVD media that boots on PCs with either BIOS or EFI. / SP2 includes ability to record data to Blu-Ray Disc media.

Windows 8 WDDM 1.2 --------- SP1 Adds support for Direct3D? 10.1, an update to Direct3D 10 that extends the API to support new hardware features, enabling 3D application and game developers to make more complete and efficient use of the upcoming generations of graphics hardware. | SP2 adds support for the 64-bit central processing unit (CPU) from VIA Technologies, which adds the ID and vendor strings for the new VIA 64-bit CPU.

Windows 2 Go in Windows 8 Enterprise -------- SP2 provides the Hyper-V virtualization environment as a fully integrated feature of Windows Server 2008, including one free instance with Windows Server 2008 Standard, four free instances with Windows Server 2008 Enterprise and an unlimited number of free instances with Windows Server 2008 Datacenter.

Windows 8 Refresh & Reset Metro based UI. Take Metro out, also take those features out. Still, let's compare --------- SP1 Adds support for new UEFI (Unified Extensible Firmware Interface) industry standard PC firmware for 64-bit systems with functional parity with legacy BIOS firmware, which allows Windows Vista SP1 to install to GPT format disks, boot and resume from hibernate using UEFI firmware. | SP1 Adds support for x64 EFI network boot.

And a whole other changes that you can check out on the links.

So take out Metro and all Metro related funcionality out of the equation. Are you still going to say that Service Packs don't add that many features and improvements?

The way you're talking, you make it sound like Windows 7 could have been a service pack. If you take out the Metro, you still get improvements that are on par with the difference between Vista, and Windows 7.

And a whole other changes that you can check out on the links.

So take out Metro and all Metro related funcionality out of the equation. Are you still going to say that Service Packs don't add that many features and improvements?

Yes they add features and improvements - of course, considering how many hundreds of Windows Updates and driver updates are included in them - but the point is they're mostly small things - a little polishing here, support for a new little standard there. They're collections of small bits of work - they don't usually add very noticeable things that everyone uses everyday.

None of them usually significantly alter the Windows Kernel, or how Windows work. And the performance improvements in the SP aren't on the same level as what we see with 8 - Refresh & Reset work outside of Metro (they're Windows Recovery Features and in the WIndows Recovery bootloader), Direct 3D 10.1 is not comparable to WDDM 1.2 (the update to WDDM 1.1 in Windows 7 is comparable).

In fact, you could most probably find a list of little technical things like that that's MUCH bigger for the changes in Windows 8 from Windows 7 soon, with more visible and important changes along with some of the much bigger architectural changes that have gone on inside Windows.

And like someone has pointed out before, what draws the line from just calling Windows 7 a service pack? After all, one could look at it as a very simple evolution of Vista with a slightly different coat of paint and faster boot up if they want too to be narrow about it.

Oh really? For example, some features of Vista SP2:

  • Adds Windows Search 4.0 for faster and improved relevancy in searches.
  • Contains the Bluetooth? 2.1 Feature Pack supporting the most recent specification for Bluetooth Technology.
  • Ability to record data on to Blu-Ray? media natively in Windows Vista.
  • Adds Windows Connect Now (WCN) to simplify Wi-Fi Configuration.
  • Enables the exFAT file system to support Coordinated Universal Time (UTC) timestamps, which allows correct file synchronization across time zones.

Then why do I constantly keep seeing "I wish Metro was optional" posts then? I mean, in almost every news that come out about Windows 8, people write that in the comments.

I wouldn't call most of those new features, rather upgraded existing capabilities and obviously additional drivers. And I see you missed the word "usually" in my reply? Apparently many people want Microsoft to improve upon Windows Aero.

It is not a finished product. It has bugs, quirks, giggles and the whole bit because it is beta.

"For the millionth time", Windows 8 has been essentially in its final state for almost a year now. The ONLY thing you will see between now and this summer's RTM are bug fixes and minor cosmetic improvements.

You are in denial if you don't realize that Microsoft NEVER makes major changes to its OS between the preview and RTM stages.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a 10g switch with a combination of copper and SPF ports and should be a fully managed switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. if your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!