Steam on Linux - Disappointing


Recommended Posts

relax and give it time broski. it's new and as all new things go.. there are inherent bumps in the road. I would like to see how you feel about it in say...oh... a year from now?

This same argument is said every year about Linux itself. 20+ yrs later and people are still saying "Give it time this will be the year of Linux".

I think all that would be needed for this to take off is for a game that's exclusive to the Linux Steam to become a hit. That said, I'm not sure if that means it would have to come from some big publisher, or if any other circumstances would have to be met.

who would do that? There's no way in hell theres ever gonna be a COD or GTA or Saints Row exclusively on Linux. The best you can hope for would be a pokemon or maybe an angry birds addon.

Plus I just jumped onto my Gentoo box and Steam installed just fine. Nothing to play though but whatever.

First of all, why is the client 32-bit only? I honestly can't remember that last time a Linux application came with only a 32-bit binary. This decision means that everyone on an x64 Linux build has to install 32-bit libraries in order to run Steam. Why not just provide a 64-bit binary and save us the bloat of having to install multilib libraries purely for Steam? I can't imagine that the difference between x86 and x64 would be so much that it'd be impossible to develop both at the same time.

The situation is the same on Windows apart from the 64 bit steam service. I'm guessing developing 2 clients side by side would increase support costs but it would be nice to see Valve throw more weight behind 64 bit computing given how many of their gamers use 64 bit versions of Windows.

Second, what's with the auto-update process? Most Linux distros have pretty solid package management. So why not just leave it to the package managers? This problem is SOLVED in Linux. Why use some [****-poor] auto-update process when mature platforms already exist for exactly this problem?

Don't keys for third party repositories have to be signed? could be that they're not really happy with having such little control over the process. Besides with the system Steam currently has you're auto updated as soon as you log in which means they don't have to support a whole bunch of people using outdated clients. If they relied on software repositories it's likely users wouldn't always update so frequently.

The rest of your complaints sound pretty much like they're explained by it being a very early development version. If you were expecting it to sparkle and have a huge library of games available after such a short amount of time in development i'd say your expectations were probably a touch too high. Steam wasn't great when it was first released for Windows but I am confident it will eventually come good on Linux.

Stop using it on an unsupported OS then, Ubuntu only for now.

It should still work on other distros. Noobuntu isn't the only one. I got it working fine on Gentoo and my friend uses his on Arch.

Sorry for the long reply, I've been AFK for a few days and haven't had chance to reply. I've replied to most of the key points. Duplicates and unconstructive comment have been omitted...

Sounds pretty mild, approximately 0% normal users care sbout dependancies unless it is causing a problem. It uses a few GBs of space, and that is the price you pay for the client and the games which need it. How big is your hard drive? 10GB? Maybe you need a bigger drive. It makes sense that they use their own auto update, standard update managers don't support the DRM which Steam needs to make their platform a reality, and using their own auto update to test their DRM laden update process makes sense.

The size of my hard disk is fine. My point is that separate builds on Linux for 32-bit and 64-bit is pretty standard. Hopefully there will be a 64-bit client by the time the beta is through. I guess I'm just more aware of it since Arch doesn't include any 32-bit libs by default, and downloads them on demand.

Regarding the updater. I'm not talking about the game update process, I accept that that has to be done through the client, I'm talking about the updater for the application itself. Whenever Steam requires an update, I see this crappy popup box that downloads and installs the update. I don't see why this can't be handled with pacman or apt or yum or <insert package manager here> unless there's some need for Valve to keep the Steam client constantly up to date, which is always possible.

Valve have said that Ubuntu is currently the only supported distro, hence it trying to use apt-get to install stuff it needs. So it not working properly on Arch isn't surprising.

Very true, but why did the game decide to do this? Using a specific package manager to download a component is needlessly limiting, especially since the Humble Bundle version of the game worked fine on every other major distro.

I think a lot of my concerns revolve around the fact that I thought that Valve were extending the beta to other distros since I was invited as an Arch user to the private beta. Unfortunately it appears this wasn't the case, I just got an invite regardless.

So what, you expect them to make a Pacman, Debian, RPM, ... -compliant update process? Nah. Makes sense they just use their own, as they have to keep complying with their contracts with the game makers.

Why not? If there's some dying need for Valve to keep the client up to date constantly, then I guess it must be done, but there are advantages to package manager support for users. It's not an insurmountable task. If the likes of NixInstaller, Google, Mozilla, Apache and Oracle can manage it, why can't Valve?

Interestingly, someone later in this thread mentions that Valve have a PPA for Steam in Ubuntu, so maybe they are doing the Package manager thing and it's falling back to some in-built auto-updater for other distros? Hopefully they're support other distros' package managers in time.

I don't care either way if they make Steam for Linux, but sometimes I think people forget what the hell a beta is.

I guess we're not allowed to complain if software is buggy? If anything, the time TO complain is during the beta, lest people keep their mouths shut and the bugs make it into final. :rolleyes:.

(Before anyone gives me crap for "not complaining to Valve", Valve are hopefully aware of all these issues since they've been brought up on the forum. I was, like I said in the OP, ranting for the mostpart).

"Fourth, and probably most importantly, where's the quality control in the games? Of all the games that are "available for Linux", in my experience about 50% are 'private betas' that need a password to play or simply don't install."

I've got a lot of linux games and they all work fine.

Store -> tab 'Linux Games' lists only linux games.

"SpaceChem trying to use apt to try and install dependencies"

Haven't seen that happen but agreed fully, should be up to steam and using config files that you set up yourself for your system/package management system.

I've been impressed with it since I got invited to the beta, seems fine to me all in all for a beta.

I've got the Linux games list up, but of those, half the one's I've tried (notably Psychonauts and Snapshot) are both in "Private Beta" meaning that I can't play them without a password. Seems kind of harsh to include them in my games list if I can't actually play them. Earlier versions of Steam tended to install just the application icon for a game, and not the game itself, meaning the game would silently fail.

Interestingly, this brings me to another thought. Games launched from within Steam tend to fail silently when they crash, and there's no way to redirect output from within the Steam client AFAICT. That'd be a nice addition.

I just find it amusing that Gabe ranted about Windows 8 being a closed platform and then of all distro's to base development on chooses Ubuntu! I'm not going to slag Ubuntu off but it's guilty of a lot of what Windows 8 is apparently guilty of, has a store that sells games, it's x64 builds are multi-libbed by default etc. Of all the distro's you can choose Ubuntu is without doubt doing it's own thing and forcing it's internal ethos on the users, just like Windows 8!

Anyway, then there's the games, some of the ports are sloppy, not Valve's fault, HiB guys are guilty of rushing ports with really silly, lazy bugs, these all have Steam keys now. Also, game choice is not very good, apart from Valve's own and a few others you can get the rest of the games elsewhere and it alleviates a lot of the problems, can get a native x64 Amnesia-TDD for example that means you don't have to multilib, then again if you use Ubuntu you don't care about multilib.

The steam client doesn't adhere to EWMH, as such won't work on tilers properly, the Valve guys were given viable alternatives to updating outside of package managers but weren't interested, actually thinking about it Ubuntu and Steam perhaps belong together and target the same users who don't care about all of this stuff, and that's fair enough I guess.

I was mad at first but now I've realised that it's a mainstream product targeted to mainstream users who typically don't care if they are decent Linux citizens or not, the type of users who think Ubuntu IS Linux, and I hate to say it but a lot of the Linux users here on Neowin fall into that category which is why most reply's on this thread don't understand the grievances OP mentioned. I don't mean this in a nasty way, but most here have never stepped outside of a DE and discovered what really sets Linux apart, and if you've not done this how would you be expected to know any different?

Agreed for the mostpart, but I bolded the thing I found extremely relevant to me. The "Steam for Linux" beta is really just a "Steam for Ubuntu" beta, with lip service paid to other distros. Regarding the ports situation I agree, but I don't really understand why the ports have gotten WORSE under Steam. Many of these games were completely functional without Steam, I wouldn't have imagined that adding Steam support would have been that big of a task.

Stop using it on an unsupported OS then, Ubuntu only for now.

Well I was invited to the private beta, so I guess they wanted me to try it. Besides, if I was using an unsupported OS, why didn't they call it "Steam for Ubuntu"?

The situation is the same on Windows apart from the 64 bit steam service. I'm guessing developing 2 clients side by side would increase support costs but it would be nice to see Valve throw more weight behind 64 bit computing given how many of their gamers use 64 bit versions of Windows.

Don't keys for third party repositories have to be signed? could be that they're not really happy with having such little control over the process. Besides with the system Steam currently has you're auto updated as soon as you log in which means they don't have to support a whole bunch of people using outdated clients. If they relied on software repositories it's likely users wouldn't always update so frequently.

The rest of your complaints sound pretty much like they're explained by it being a very early development version. If you were expecting it to sparkle and have a huge library of games available after such a short amount of time in development i'd say your expectations were probably a touch too high. Steam wasn't great when it was first released for Windows but I am confident it will eventually come good on Linux.

I hope so. I know it's only a beta, but it's certainly buggier than a lot of betas I've tried in recent years. I guess they have a lot on their plate though and I think my expectations probably were too high, which is the problem here. I'm looking forward to the final release, I just hope the final support extends beyond -buntu.

I just want to point out that I'm not hating the Steam on Linux beta, after all, I'm glad it's coming. I think I just expected more from this beta.

Thanks for the input folks, even if your views differ to my own, it's still good to hear em :)

I guess we're not allowed to complain if software is buggy? If anything, the time TO complain is during the beta, lest people keep their mouths shut and the bugs make it into final. :rolleyes:.

(Before anyone gives me crap for "not complaining to Valve", Valve are hopefully aware of all these issues since they've been brought up on the forum. I was, like I said in the OP, ranting for the mostpart).

Oh, you're absolutely allowed to complain, but what does complaining on a forum away from Valve attempt to solve? anything? a need to rant because it's not working the way you want it to during a beta?

And you should speak up, even if other people have already submited your issues, that's how they weigh if the issues are a concern or not, if only 3-4 people complain, hey, that's not a huge issue and they'll

work on other stuff first, the more people speak up and complain the more likely the issues will be addressed.

A few things to note:

- Steam on Linux will pretty much start with only Valve's offerings fully functional. Each platform release for Steam has begun this way.

- Let's face it, Valve's Steam coders have always been terrible. The bar has merely been raised, and Steam isn't any less terrible by today's standards, than it were ten years ago.

- The reasoning behind our Steamy fever has gradually shifted. For many, it is less about the games, and more about the community behind those games. Many of us Linux enthusiasts will see the native client as a godsend after using the glitchy mess that is Wine'd Steam. As the userbase becomes apparent, the games will follow.

- Linux and its support has almost matured to a point where it is on par with Windows in stability while tweaking. I installed Fedora 18 the other day, and decided to cross my fingers before testing out AMD's newest proprietaries. Amazingly enough, Gnome 3 was 100% functional, and TF2 performed better than my Windows installation.

- That big, Steamy pile'o'crap we use was actually excreted from the white dwarf "Gabe Newell," and being of great mass, others are bound to gravitate to his new position in Ubuntu's multiverse. Give it two years and we'll see a healthy solar system with a few dozen developers orbiting.

I would say even though it's pretty heavy on ubuntu at the moment give it time. They picked ubuntu as it's the most widely installed distro for end users. However once it gets rolling I would expect it to roll out to the other major distros with fedora likely to be next

I would say even though it's pretty heavy on ubuntu at the moment give it time. They picked ubuntu as it's the most widely installed distro for end users. However once it gets rolling I would expect it to roll out to the other major distros with fedora likely to be next

Arch first. Have you even seen what kind of a userbase Steam has? The majority is Arch, not Ubuntu. Us Fedora have little to no representation :(

Arch first. Have you even seen what kind of a userbase Steam has? The majority is Arch, not Ubuntu. Us Fedora have little to no representation :(

Arch is a bit of a noob/half gentoo, so it'll never appeal to the masses that want to game. Imagine valve trying to get people on it 'Just download this ISO, boot from it and partition your hard drives, mount the filesystems and use pacman to setup a base installation then install a bootloader and reboot without the disk or fire up links if you get stuck!'... Everyone would look around in complete confusion and not have a clue what they were talking about and just use windows.

Ubuntu on the other hand, despite it being crap in my opinion, really can be used by anyone, there's a GUI installer, it'll automatically resize your windows partitions and allow you to dual boot which is the user valve is aiming at, right now at this moment in time.

Arch is a bit of a noob/half gentoo, so it'll never appeal to the masses that want to game. Imagine valve trying to get people on it 'Just download this ISO, boot from it and partition your hard drives, mount the filesystems and use pacman to setup a base installation then install a bootloader and reboot without the disk or fire up links if you get stuck!'... Everyone would look around in complete confusion and not have a clue what they were talking about and just use windows.

Ubuntu on the other hand, despite it being crap in my opinion, really can be used by anyone, there's a GUI installer, it'll automatically resize your windows partitions and allow you to dual boot which is the user valve is aiming at, right now at this moment in time.

Half Gentoo? That's the first time I ever herd Arch being that.

Why would Valve ever do that?

Arch is a bit of a noob/half gentoo, so it'll never appeal to the masses that want to game. Imagine valve trying to get people on it 'Just download this ISO, boot from it and partition your hard drives, mount the filesystems and use pacman to setup a base installation then install a bootloader and reboot without the disk or fire up links if you get stuck!'... Everyone would look around in complete confusion and not have a clue what they were talking about and just use windows.

Ubuntu on the other hand, despite it being crap in my opinion, really can be used by anyone, there's a GUI installer, it'll automatically resize your windows partitions and allow you to dual boot which is the user valve is aiming at, right now at this moment in time.

What you're implying is that Valve expect people will switch to Linux just to game, when the overall goal is to merely blur the gaming line between the operating systems. Only the bandwagony types will switch right away for the sake of Gabe's enthusiasm. What Valve needs to do right now is attract those of the Steam userbase that already like to use Linux on a regular basis.

See, it's more about statistics right now than anything. Anybody playing TF2 on Windows now will likely not switch to Linux just to play TF2, but with some nice steam statistics and a streamlined approach to releasing on the third platform, developers might open their minds a little bit to the idea.

As it stands, Arch Linux is the largest group of Steam Linux users. Valve will follow suit.

What you're implying is that Valve expect people will switch to Linux just to game, when the overall goal is to merely blur the gaming line between the operating systems. Only the bandwagony types will switch right away for the sake of Gabe's enthusiasm. What Valve needs to do right now is attract those of the Steam userbase that already like to use Linux on a regular basis.

See, it's more about statistics right now than anything. Anybody playing TF2 on Windows now will likely not switch to Linux just to play TF2, but with some nice steam statistics and a streamlined approach to releasing on the third platform, developers might open their minds a little bit to the idea.

As it stands, Arch Linux is the largest group of Steam Linux users. Valve will follow suit.

Actually probably their logic is as follows:

Ubuntu is maintained by Canonical which also is an ENTRY (casual) level Linux unlike Arch that is more suited to the person who wants to install and configure it the way they want it.

Canonical also is heavy into the support of Debian.

Start out with support for the simple linux user then fork it out for others.

https://wiki.archlin....php/Arch_Linux

Arch Linux

Arch Linux is an independently developed, i686/x86-64 general purpose GNU/Linux distribution versatile enough to suit any role. Development focuses on simplicity, minimalism, and code elegance. Arch is installed as a minimal base system, configured by the user upon which their own ideal environment is assembled by installing only what is required or desired for their unique purposes. GUI configuration utilities are not officially provided, and most system configuration is performed from the shell and a text editor. Based on a rolling-release model, Arch strives to stay bleeding edge, and typically offers the latest stable versions of most software.

Which the entry level user just wants to -- Click on the .deb file and the OS automatically grabs what it needs. (Unlike with Arch where you may have to manually install the needed libraries.)

Don't get me wrong- I have used Arch and it is great but for the beginner Ubuntu is the easier start for a new user.

that is probably why they started with Ubuntu.

That and Ubuntu is supported by a company unlike Arch which is User / Community driven/based.

(which means there is someone to contact when their product stops working to help to fix it and get the fix out to the masses unlike the other where they may have to wait on the Community of users to work on the fix)

(I am sure you will argue that- which I can understand your point about more Arch users would want it, but that was probably their logic as to why UBUNTU)

Since it's a beta, I'm pretty sure they'd be delighted to hear your feedback, if you send it to the right place. That's what betas are for, after all ;)

And Arch for a Linux newbie? Perfectly fine for a willing to learn newbie. Would be catastrophic for a clueless one, though :p

The Distro "wars" is probably a large part of why it's taken Valve this long to bring Steam to Linux.

Frankly, if you're willing to go through the relative hassle of installing Arch, but hate having to do a little work to get the Steam Beta installed, then I have no idea what possessed you to install Arch in the first place.

Disclaimer: This is basically a rant thread.

So I've been using the Steam Linux beta for a few weeks now, and I've come to following conclusion: The Steam Linux beta sucks.

It's not like I don't appreciate what they're doing, I mean after all, Valve are the only publisher that's really taking Linux (except they're not, I'll discuss that later), but still, the execution of the whole thing is farcical.

First of all, why is the client 32-bit only? I honestly can't remember that last time a Linux application came with only a 32-bit binary. This decision means that everyone on an x64 Linux build has to install 32-bit libraries in order to run Steam. Why not just provide a 64-bit binary and save us the bloat of having to install multilib libraries purely for Steam? I can't imagine that the difference between x86 and x64 would be so much that it'd be impossible to develop both at the same time.

Second, what's with the auto-update process? Most Linux distros have pretty solid package management. So why not just leave it to the package managers? This problem is SOLVED in Linux. Why use some [****-poor] auto-update process when mature platforms already exist for exactly this problem?

Third, why does the client feel compelled to screw with my cursor. This is probably a problem with my setup rather than Steam, but it's the only app on my system that insists on reversing my mouse cursor. Oddness.

Fourth, and probably most importantly, where's the quality control in the games? Of all the games that are "available for Linux", in my experience about 50% are 'private betas' that need a password to play or simply don't install. To make things worse, it doesn't actually tell you that when you buy the game, so you are at risk of buying a game you can't actually play. The funniest thing I find about this is that a lot of the games that don't work are also former Humble Bundle games, so I can play the game perfectly well without Steam, but then can't play the Steam version of the same game. What the hell is up with that?

This inconvenience is compounded by failures like, for example, SpaceChem trying to use apt to try and install dependencies on my Arch install (for those that don't know, that doesn't work), and including libraries that don't work on 64-bit installs. There are threads with distro-specific hacks to get games working, but why isn't Steam doing this for us? I don't expect them to cater to every OS, but they could at least give us some hints. Make the developers provide a list of dependencies, and then check against installed libraries to determine which ones I need to install to get a game to work, and then tell me.

The games overall seem to be the 32-bit versions of the games (which I guess makes sense since the client is too), so I'm installing a lot of 32-bit libs for all the games too. It's gradually turning my Arch install into a glorious mess of libraries. Not really an issue per se, but an annoyance for someone like me who tries to keep a minimal install as much as possible.

I don't know, I guess this beta is giving me a bit of a bitter after-taste. They're touting it as the "Steam Linux beta", when in reality it should just be the "Steam Ubuntu Beta" since non-Ubuntu user's are pretty much out there on our own hacking it together to get it to work.

Overall, I'm finding more success playing games outside of Steam than I am within it. One of the best things about the Windows client is the convenience factor. On Linux I just get the overall impression we're testing the steam box client, and getting a buggy DRM client out of it. I don't think Valve are really taking Linux seriously like they're making out, they're just getting us to iron the bugs out of the client so they can release a bug-free console. Linux games will be a fortunate side effect of the Steam box, but not the primary focus IMO.

Not impressed.

sounds like the steam BETA is not for you that's all.

I have it running in fedora and not a single issue not one at all

works just as good as it does in windows for me.

32-64bit stuff you are talking about is a non issue for 99.99% of every Linux user who cares if its 32bit you can not tell the diff

This topic is now closed to further replies.
  • Posts

    • PDF-XChange Editor 11.0.1.0 by Razvan Serea PDF-XChange Editor is a comprehensive PDF editor that allows you to create, view, edit, annotate, and digitally sign PDF documents with ease. With advanced features like OCR, document security, and PDF optimization, PDF-XChange Editor is a powerful tool for both personal and professional use. Whether you need to edit text, images, or links, or add comments, stamps, or watermarks, PDF-XChange Editor provides all the necessary tools to make your PDFs look perfect. Additionally, it supports a wide range of file formats, including PDF, XPS, and DOCX, making it easy to convert and share your documents. PDF-XChange Editor key features: Edit text and images in PDF documents Add and remove pages from PDF files Annotate and markup PDFs with comments, highlights, and stamps Use OCR to convert scanned documents into searchable text Create and fill out PDF forms Sign and certify PDF documents digitally Add and edit hyperlinks within PDFs Extract text and images from PDF files Batch process multiple PDF files at once Customize the interface to your preferences Work with multiple documents in tabs Convert PDFs to other formats such as Word, Excel, and HTML Use advanced redaction tools to permanently remove sensitive information Add customizable headers and footers to PDFs Merge multiple PDF documents into a single file Split PDF documents into multiple files Add watermarks to PDF documents Use the measurement tools to calculate distances and areas in PDFs ....and much more PDF-XChange Editor 11.0.1.0 changelog: Fixed a crash in the new Open/Save dialog box when creating a new folder in an unavailable network path. (49552) Fixed a rare/infrequent crash on some dynamic XFA forms after changing their field values. [installer] Fixed an issue where shortcuts were lost during an upgrade from the previous version. [installer] Fixed an issue preventing migration of serial keys during updates from version 10. Fixed the issues with the shell context menu after installation of version 11. Fixed the issue with filtering comments. (49478) Fixed the issue that caused "Error [IO subsystem]: Invalid access mode." when converting PDFs to MS Office formats. Fixed an issue with the context menu position on some multi-monitor systems. (48467) Fixed an issue with handling complex custom file filters, displayed by JS, in the new Open/Save Files dialog box. (49486) Fixed several issues with the new 'Select Folder' dialog box. (49505) Fixed an issue with the new custom 'Open File' dialog box when using double-click to open it. (49498) Fixed an 'infinite' loop/proliferation in the 'Open Files' and 'Manage Places' dialog boxes. (49526) Fixed an issue with handling the mouse wheel inside the document "Find" box. (49539) Fixed an incorrect behaviour in the 'Go back (Alt+Left)' button in the new Open/Save Files dialog box. (49510) Fixed an issue with the shortcut keys (Alt+Left/Right) after navigating via breadcrumb paths in the new Open/Save Files dialog box. (49554) [installer] Fixed an issue with redrawing the progress text in the EXE installers. Fixed the issue where a mouse click outside of the polyline/polygon context menu during annotation creation would cancel the annotation. (49475) We switched back to using the system Open/Save/SelectFolder dialog box by default, instead of using the new one, because some popular features such as the QuickAccess/Recent items are missing in the new version. These will be added in a future release. Replaced the 'Extension' column in the new Open/Save File dialog box with a more user-friendly 'Type' column. Also fixed some issues when handling the 'Show file extension' option. (49497) Added the ability to authenticate local network shares in the new Open/Save Files dialog box. (49557) Improved the handling of dates after 01.01.2030 in XFA files - now such dates are stored properly when set via the dropdown widget. Flags NoZoom and NoRotate are now respected for only a limited subset of annotations. Download: PDF-XChange Editor (64-bit) | Portable ~300.0 MB (Shareware) Download: PDF-XChange Editor (32-bit) | Portable ~200.0 MB Download: PDF-XChange ARM64 | 276.0 MB Download: PDF-XChange Portable @PortableApps.com | 97.0 MB View: PDF-XChange Editor Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still 3x what it should cost. So, it seems the trick is to increase price by 6x so that a reduction in price back to 4x looks like a steal. "You savvy shoppers win again!" I'm glad I'm not in a desperate spot to actually even need this overpriced crap. Hopefully, it comes back down by the time for when (or if) I ever do.
    • Although AI is great and has it's use cases they likely have massively overhyped it and it has not delivered as per their expectations. I fully expect them to start saying the same things again when it does get to a certain level of intelligence!
    • Microsoft wants to end printer driver headaches with Windows Ready Print by Usama Jawad A few days ago, Microsoft released Windows 11 Experimental build 26300.8553, bringing a ton of enhancements such as Start menu customization, search improvements, Taskbar polish, and other minor UI tweaks. Another relatively major enhancement snuck deep within the change log was related to upgrades to the Windows printing experience. Now, Microsoft has shared more details about these benefits. For starters, Microsoft has renamed its Modern Print Platform to Windows Ready Print. The company believes that this name highlights its shift in strategy, which now focuses on modernizing, securing, and streamlining the printing experience for Windows devices. Some of the upgrades present in Windows Ready Print have already been seeded to customers and partners. This includes ending support for third-party printer drivers via Windows Update and transitioning towards the Internet Printing Protocol (IPP) and the native Windows IPP printer driver. In line with these changes, new printer installations will default to Windows Ready Print on eligible devices starting from July 2026. However, Microsoft recognizes that not all environments will be able to migrate to this platform immediately, so it will allow users to choose between installing the printer via Windows Ready Print or the traditional OEM process. Users will be able to toggle this configuration through Settings > Bluetooth & Devices > Printers & Scanners > Printer preferences. This control applies only to new printer installations, and its functionality can also be modified via Group Policy as follows: Launch Group Policy Editor Navigate to Local Computer Policy -> Administrative Templates -> Printers Find and select 'Configure Windows Ready Print driver ranking' -> double click to open it Select 'Enabled' (if you wish to enable Windows Ready Print driver selection) or 'Disabled' (if you wish to explicitly disable Windows Ready Print driver selection). Select Apply Select OK Similarly, if you set up Windows protected print mode through the same setting in Windows 11, it will also default to using Windows Ready Print exclusively. Microsoft hopes that these improvements will help eradicate dependency on OEM-specific driver installation processes and simplify printer installations. We'll likely find out more about other tangible benefits in the coming months.
  • Recent Achievements

    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      231
    3. 3
      +Edouard
      138
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!