Chromebooks don’t normally run Windows software—that’s the best and worst thing about them. You don’t need antivirus or other Windows junk…but you also can’t install Photoshop, the full version of Microsoft Office, or other Windows desktop applications.
Luckily, there are ways to use Windows desktop programs on a Chromebook: either running them remotely on an existing Windows system, through various Android workarounds, or getting your hands dirty in developer mode and running them on your Chromebook itself.
Option One: Access a Windows Desktop Remotely
Google’s Chrome OS is meant to be a lightweight operating system, so why not embrace that? We recommend running Windows software on your Chromebook by accessing a remote Windows computer and doing it there. There are two different approaches you can take.
Access Your Own Windows Computer: If you already have a Windows computer, you can access it remotely and use it to run your Windows software. You can do this using Google’s Chrome Remote Desktop beta webapp. You’ll be able to connect to your Windows desktop from your Chromebook (or any other computer running Chrome) and have complete control over your remote machine, allowing you to work with Windows applications.
The downside here is that your Windows computer will have to be running at home whenever you need to access it from your Chromebook. It’s a convenient solution for personal use, but businesses won’t want to manage a separate Windows computer for each Chromebook user.
![]()
Host Windows Applications on a Remote Server: Chromebooks can use Citrix Receiver to access Windows applications hosted on a Citrix server, or use an RDP client to access a remote desktop hosted on a Windows server. This is ideal for businesses that want to host their own servers and give their users light, thin clients that allow them to remotely access the hosted software.
As a home user, you could choose to purchase service from a company that would host a Windows desktop for you and allow you to access it remotely, but you’d probably be better off using your own Windows computer instead.
Option Two: Use Developer Mode and Install Wine
Wine is an open-source compatibility layer that allows Windows applications to run on Linux and macOS. Wine is desktop software, and there isn’t a version of Wine designed for Chromebooks…but there are workarounds.
Since Chrome OS is based on Linux, there are two ways to run Wine on your Chromebook: using Crouton to run it in Linux, or by using the new Wine Android app.
Important: Wine in Linux won’t run on ARM Chromebooks, and the Android version only supports Windows RT apps. Wine should work properly on Intel Chromebooks, however.
Use Wine with Crouton: To install the desktop version of Wine, you’ll need to enable developer mode and install Crouton to get a Linux desktop alongside your Chrome OS system. You can then install Wine on the Linux desktop and use it to install Windows programs just as you’d use Wine on a typical Linux desktop.
This would allow you to run the standard version of Microsoft Office on a Chromebook, although you’d be better off with Microsoft’s official Office Web Apps or Android apps—unless you require advanced features.
Whenever you want to use a Windows program, you could just switch between your Chrome OS system and Linux desktop with a keyboard shortcut—no need for rebooting.
Use Wine for Android: Wine also has an Android app that’s still currently in beta, but if you have a Chromebook that runs Android apps, it can allow you to run Windows programs without installing Crouton. It’s not yet available in the Google Play Store, so you’ll need to put your Chromebook in developer mode and sideload the APK.
Once Wine is installed on your Chromebook, just launch the app like normal get access to a minimal, emulated version of Windows. Keep in mind that this is still very much in beta, so it doesn’t work perfectly. That said, I would recommend at least trying this option before going through the trouble of setting up Crouton if all you plan on doing is using it for Wine.
Wine isn’t perfect, so it won’t run every Windows application and may not run some applications without manual tweaking. Consult the Wine application database for more information about supported applications and tweaks you may need.
Option Three: Use Developer Mode and Install a Virtual Machine
RELATED:4+ Ways to Run Windows Software on Linux
If Wine doesn’t support the program you want to run, or it’s just too much of a hassle, you can also run a Windows virtual machine from the Linux desktop with Crouton. Much like the above option, you’ll need to enable developer mode and install Crouton to get a Linux desktop alongside your Chrome OS system, then install a virtualization program like VirtualBox. Install Windows inside VirtualBox just as you would on a typical computer—you can switch back and forth between your Chrome desktop and Linux desktop with a keyboard shortcut.
Important: Typical virtual machine software like VirtualBox won’t function on ARM Chromebooks. You’ll want to have an Intel-based Chromebook to try this out.
Virtual machines are the heaviest way to do this, so you’ll need powerful enough hardware to drive the virtual machine software, Windows, and your desktop applications. Newer Chromebooks modern processors may be able to handle this better than older, slower Chromebooks. Virtual machines also take up a lot of disk space, which Chromebooks don’t often have—not a good combination.
Option Four: Use CrossOver for Android
If you’re using a Chromebook that supports Android apps, an Android app called CrossOver will let you run Windows programs alongside your Chrome apps. It’s still beta, but early testing has been positive.
CrossOver works similarly to Wine on Chrome OS, but it takes more of a hands-on approach in walking you through installing applications. When you open the app, you can search for specific Windows software and it will walk you through installing them. It will search for the appropriate installation files and even download them for you in most cases. It’s pretty simple to use.
Once the application has been installed, you can run it alongside your Chrome apps as if it were native. In my experience with CrossOver, apps were hit and miss—which is to be expected since the app is still in beta. It still shows a lot of promise for the future of Windows software on Chromebooks, especially if you only need one or two specific programs.
Option Five (Sort Of): Run Linux Software in Developer Mode
Lastly, you may not need to run a Windows program at all—many Windows programs have their own Linux versions, and can run on a Chromebook using Crouton’s Linux desktop without much fiddling. For example, if you want to run games on a Chromebook, Steam for Linux offers many games for Linux, and its catalog continues to expand. So this technically isn’t “running Windows software”, but in some cases, it’s just as good.
Bear in mind that many Linux programs, such as Minecraft, Skype, and Steam, are only available for Intel x86 processors and won’t run on devices with ARM processors.
Can I Just Install Windows on My Chromebook?
RELATED:How to Install Windows on a Chromebook
I know, none of the above options are really ideal. If you find yourself wishing you could just install Windows on your Chromebook…well, you might be able to. There are some projects out there that allow users to install Windows, but it’s a pretty in-depth process. Not only that, it only works on a specific set of Intel Chromebooks, so the majority of the options out there don’t actually have support. But check out that guide for more information, if you’re curious.
Otherwise, you’re better off using one of the options above—or just getting a Windows laptop, if you absolutely need to.
READ NEXT
Between web apps and Android apps in Chrome OS, there’s a lot you can get done on Chromebooks. However, there still might be certain things about Windows you miss.
You might not have thought it was possible, but you have a few different options for bringing some of that Windows goodness to your Chrome OS machine. There are a multitude of ways to make this work — and we can show you where to go. Here’s how to use Windows on a Chromebook!
Before you begin
Before setting off on this adventure, there are a few important caveats to getting Windows up and running on your Chromebook. Most importantly, messing with your operating system, firmware, and BIOS can have serious effects on your system. You’ll want to back up any important data away from your computer before you begin.
If something does happen and you find yourself unable to use your Chromebook, you can create a USB drive from another computer to try and recover the system. This will erase all of your data though, so make sure to back up anything that isn’t saved to Google Drive.
With that out of the way, let’s begin with the first (and easiest) method.
Method 1: Free Online Apps
If you are primarily interested in accessing apps from the Office suite and don’t really care about any of the other apps offered on Windows 10, this is by far the easiest option and you can do right from the Chrome browser.
Step 1: Launch the Chrome browser and navigate to this Microsoft site.
Step 2: Here you will see the selection of apps available for Office Online. Basically, Microsoft knows that certain core apps are very important for professionals and students, so they want people to be able to access them from any operating system. This is why they put up free online apps for options like Word, Excel, PowerPoint, Sway, Mail, Calendar, OneDrive, and more.
Step 3: Select the app or apps that you want to use. A version will open in your Chrome browser and you will be able to start using it. Take note that these online versions won’t have all the capabilities that you would get with something like Office 365. However, they should work for most purposes.
Method 2: Chrome Remote Desktop
The Chrome Remote Desktop is an extension that simply allows you to access another desktop while using your Chromebook. Somewhat like a virtual machine, this will open a window that shows an entirely different operating system that you can use. The key to this method — and the caveat — is that you need another Windows 10 machine connected to the internet that you can link to. That’s the only way this works. Obviously, this won’t be possible in some Chromebook situations, but if you have a Windows computer around, this can be an effective workaround.
Step 1: Navigate over to the Chrome Web Store and download the Chrome Remote Desktop extension on your Chromebook. Then head over to your Windows computer, pull up your Chrome browser, and make sure it’s updated with the same capability.
Step 2: Starting on your Windows computer, head over to your Chrome apps and select Chrome Remote Desktop, then choose Get Started. From here, choose Share. This will create an access code and ask you to define the computer you want to connect to. Email that code to yourself so that you will remember it.
Step 3: Now switch to your Chromebook. Start the Chrome Remote Desktop — this time it should see your Windows computer as an option to select and connect to. Select it, and input the access code that you sent yourself. Then click Connect.
Note: This is a very good remote desktop app, but remote desktop solutions still have their pitfalls. They are highly dependent on internet connections and can experience delays at times. This works best if you have high-speed internet all the way between your computers.
Method 3: CrossOver
CrossOver, by CodeWeavers, is a software solution that allows you to run specific OS apps on other operating systems. Thanks to the latest update, that now includes running Windows apps on your Chromebook. Before you get all excited, there are a few things to keep in mind before moving forward. First, it’s important to note that the Chrome OS version is still in beta. You can try it out, but it’s not guaranteed to be bug-free and easy-peasy for a little while yet.
The second issue is that because of the software requirements involved, this download won’t be available for everyone. Specifically, you can only run it on Intel-based Chromebooks and if you want to involve any Android devices or apps, they need to be compatible with Android 5.x or later. Also, certain functions like mouse locking (using often in FPS games) won’t function.
The good news is that because the software is currently in beta, it’s free to try. Here’s what you need to do:
Step 1: Head over to Google Play and choose to install the CrossOver on Chrome OS Beta. This will install a new icon made of two semicircles on your dashboard. When you click on it, make sure to allow it to access your media and files on your Chromebook.
Step 2: Make sure you a copy of the application’s installation file in your downloads folder, even if it won’t currently work.
Step 3: When CrossOver is launched, the easiest way to search for Windows software is to use the search bar in the top of the window and just type in the name of what you want to use. Software like Quicken, as well as DirectX applications all work, so search for anything you want.
Step 4: In many cases, you can confirm the software you want, and CrossOver will begin the installation process with no trouble. In some cases, you may have to choose the right installation file from a list, so pay close attention to file names and make sure you are choosing the one that you want. You may also have to consent to License Agreements and similar contracts at this time.
Step 5: After the installation is done, you should be able to launch the installation directly. Keep in mind that large programs will take up significant space, which not all Chromebooks have. Fortunately, there are ways to use Android apps on Chromebook and save space.
Google’s AltOS mode
Interestingly, it may soon be much easier to run Windows on a Chromebook, at least when it comes to certain models. Inspection of code and code comments has shown discussion of Windows hardware kits and names that indicate native support for Windows software.
The latest news on this capability indicates it will be called “dual boot” when the feature comes to users. This would be a feature available in upcoming versions of Chrome OS for Pixelbooks. Most recently, there’s evidence that Google has been testing the dual boot mode, switching it back and forth to make sure that there are no security issues with the feature, a sign that we may not have much longer to wait for this functionality to appear.
This means you may have to pay for a high-end Chrome machine to get the advantages of the feature, as well as devote a lot of hard drive space (around 40GB at the latest estimation), but it could be well worth it if you need both Chrome and Windows. If this dual boot option is ready, then we are most likely to see it on the Pixelbook 2, which has not yet been announced but could be close to release.
Editors' Recommendations
Every organization, big or small, has a hidden asset: Old laptops and desktops that have outlived their usefulness, are too slow for today’s software or use less secure operating systems. Admittedly, that doesn’t sound like anything of great value. But it’s easy to breathe new life into those machines by converting them into Chromebooks.
Because the Chrome OS is lighter than Windows and macOS and requires fewer resources, older systems that bog down with Windows 10 or macOS Mojave often work just fine as Chromebooks. That means that systems with slower CPUs, less RAM and smaller hard drives — the ones that no one in your organization wants to use — can get a second lease on life.
I’m going to show you how to use Neverware’s CloudReady Enterprise Edition to turn an old Mac or Windows PC into a Chromebook; there are also versions of the software for schools and home use. I’ll be using the three-week trial software, which can be converted to the full licensed version, which includes support, for $49 a year. The software has its own dashboard but can also use the Google Admin Console to monitor, manage and update a company’s worth of Chromebooks; that adds $50 a year to the cost.
While I’ll be using a Toshiba Satellite Radius laptop, desktops work just fine. In fact, I recently converted a Lenovo all-in-one system that refused to take Windows 10 updates. You’ll need an 8GB USB flash drive to install the software, about 30 minutes and, of course, an old PC that you want to convert. In the steps described below, the assumption is that you are converting a Windows machine, but the process is similar for macOS conversions.
One final note before we begin: For the sake of readability, throughout this story I say your computer will become a Chromebook that runs Chrome OS, but that’s not strictly true. As my colleague JR Raphael explains, CloudReady uses Google’s Chromium OS — the technology that underlies Chrome OS — to turn your device into a Chromebook-like system with some limitations. (More on that later.)
Step 1: Getting started
Start by seeing if your system is on CloudReady’s compatibility list at Neverware’s site. The list has hundreds of systems, but if your system isn’t on it, I suggest making the conversion flash drive and trying it out anyway. Chances are it will work.
One last preliminary: The software formats the system’s drive, essentially making previous data inaccessible. Still, you might want to shred its contents, just in case there’s something confidential on it.
Step 2: Getting the software
Using a Windows 7 or newer computer (it need not be the machine you are going to convert), go to Neverware’s download site and fill out the form, accept the company’s license terms and pick a password; you’ll need it later. I suggest reading the Install Guide to help make the process more efficient. (Note that this step can also be done with a computer running macOS. I couldn’t find any information about version on Neverware’s site, but there is a warning that you must use the free software called Unarchiver to unzip the CloudReady file that is created, due to a bug in macOS.)
At this point, the installation sequence takes over. After running the “Check Network” routine, click “Next: Build the Installer” at the page’s bottom right.
Step 3: Creating the installation flash drive
Click “Download USB Maker” to get the 42MB installation file that makes the installation flash drive. After clicking “Next” in the lower-right corner and entering your email address and password, pick the 32- or 64-bit version.
After clicking “Next,” insert the USB flash drive you want to use. Click “Next” to download the software from CloudReady’s servers. The software extracts the compressed image and loads the software on the flash drive. After about 15 minutes, it’s done; click “Finish.”
Step 4: Starting the conversion
Plug the flash drive into the machine you want to convert and turn on the PC. Before the OS starts loading, go to the system’s BIOS utility. For the Radius, I pressed the Function-12 key to bring up the Toshiba’s Startup Utility. Each machine is slightly different, with some using FN-1, FN-2, FN-9 or FN-10; Macs require pressing the Option and Command (cloverleaf) key.
Next, I changed the settings so that the system goes first to the USB port for its startup software. I also disabled the Secure Boot feature that prevents booting from an external drive. When everything is done, I suggest changing these settings back.
Step 5: Setting the system upChrome Os Download
Start the machine up, and the CloudReady software loads from the flash drive. It asks what language you’d like to use and then your Wi-Fi network and password.
This is just a preliminary, followed by clicking “Install CloudReady.” The software then creates a new system. This takes about 10 minutes.
Step 6: Welcome to Chrome
When the machine shuts down, it’s complete. After taking the flash drive out of the machine, start it up. It again asks for your Wi-Fi network and password, followed by a software update.
Congratulations, the system is now a Chromebook and it asks you to log into a Google account. The screens look just like any other Chromebook except that the Chrome icon is blue instead of yellow, red and green.
I used the system to nose around the web, read and reply to hundreds of emails, watch videos and listen to podcasts. I used Chrome apps, such as Mind Map, and saved some images on my Dropbox storage account. The best part was opening and working on collaborative files in Google Docs. I reviewed and reworked portions of a technical report and marked up a spreadsheet.
Step 7: Checking out Chrome
A big bonus is that every part of the Radius system worked without any intervention. It connected to my company’s Wi-Fi infrastructure, its Bluetooth radio worked with a Logitech Mini Boombox and the system’s touchscreen, keyboard and touchpad responded perfectly.
While it’s close, a CloudReady system isn’t exactly a full Chromebook. To start, Android apps won’t load on the CloudReady system, and there’s no vocal searching, logging in as a supervisor or translating highlighted items. Of more concern, IT pros can’t use PowerWash to remove user data, but you can just run the flash drive’s software to start over for a new user. There are other differences as well. See JR Raphael’s complete list of the differences between CloudReady and Chrome OS.
Step 8: Discovering extras
The center of attention may be the Chrome interface, but the Enterprise Edition’s dashboard page is the focal point for IT folks. Logically laid out, front and center you can track licenses along with their expiration date. Along the left is a powerful set of detail sections that make it easy to focus on specific items, such as Plugins for Flash and other activities, and a list of users with their login names. On the other hand, the design is simplistic and ignores opportunities for synergy, such as streamlining the process by putting together the device and user data with the license information.
![]()
While you can get and use the software for free, companies that pay the $49 a year to license the software get a lot more support, including access to Neverware’s online help resources that include a Forum and a Knowledge Base with lots of problems and solutions. There's also the current three most popular tips that might help avoid or get out of trouble. Technicians are available for phone help from 8:30 a.m. to 5:30 p.m. (Eastern time), Mondays through Fridays, or via email.
All in all, the CloudReady software is as close to corporate recycling as it gets these days. It can turn junk and castoffs that are collecting dust into powerful tools that your company can use every day.
Read this next: 40 Chromebook tips for maximum productivity
Chrome OS is a Linux kernel-based operating system designed by Google. It is derived from the free softwareChromium OS and uses the Google Chrome web browser as its principal user interface. As a result, Chrome OS primarily supports web applications.[9]
Google announced the project in July 2009, conceiving it as an operating system in which both applications and user data reside in the cloud: hence Chrome OS primarily runs web applications. Source code and a public demo came that November. The first Chrome OS laptop, known as a Chromebook, arrived in May 2011. Initial Chromebook shipments from Samsung and Acer occurred in July 2011.
Chrome OS has an integrated media player and file manager. It supports Chrome Apps, which resemble native applications, as well as remote access to the desktop. Android applications started to become available for the operating system in 2014, and in 2016, access to Android apps in the entire Google Play Store was introduced on supported Chrome OS devices. Reception was initially skeptical, with some observers arguing that a browser running on any operating system was functionally equivalent. As more Chrome OS machines have entered the market, the operating system is now seldom evaluated apart from the hardware that runs it.
Chrome OS is only available pre-installed on hardware from Google manufacturing partners, but there are unofficial methods that allow it to be installed in other equipment.[10][11] An open source equivalent, Chromium OS, can be compiled from downloaded source code. Early on, Google provided design goals for Chrome OS, but has not otherwise released a technical description.
History[edit]
Google announced Chrome OS on July 7, 2009,[1] describing it as an operating system in which both applications and user data reside in the cloud. To ascertain marketing requirements, the company relied on informal metrics, including monitoring the usage patterns of some 200 Chrome OS machines used by Google employees. Developers also noted their own usage patterns. Matthew Papakipos, former[12] engineering director for the Chrome OS project, put three machines in his house and found himself logging in for brief sessions: to make a single search query or send a short email.[13]
Chrome OS was initially intended for secondary devices like netbooks, not as a user's primary PC.[14][15] While Chrome OS supports hard disk drives, Google has requested that its hardware partners use solid-state drives 'for performance and reliability reasons'[16] as well as the lower capacity requirements inherent in an operating system that accesses applications and most user data on remote servers. In November 2009 Matthew Papakipos, engineering director for the Chrome OS, claimed that the Chrome OS consumes one-sixtieth as much drive space as Windows 7.[17] The recovery images Google provides for Chrome OS range between 1 and 3 GB.[18]
On November 19, 2009, Google released Chrome OS's source code as the Chromium OS project.[19] At a November 19, 2009, news conference, Sundar Pichai, at the time Google's vice president overseeing Chrome, demonstrated an early version of the operating system. He previewed a desktop which looked very similar to the Chrome browser, and in addition to the regular browser tabs, also had application tabs, which take less space and can be pinned for easier access. At the conference, the operating system booted up in seven seconds, a time Google said it would work to reduce.[16][14][20][21] Additionally, Chris Kenyon, vice president of OEM services at Canonical Ltd, announced that Canonical was under contract to contribute engineering resources to the project with the intent to build on existing open source components and tools where feasible.[22]
Early Chromebooks[edit]
In 2010, Google released the unbranded Cr-48 Chromebook in a pilot program.[23][24] The launch date for retail hardware featuring Chrome OS was delayed from late 2010[25] until the next year. On 11 May 2011, Google announced two Chromebooks from Acer and Samsung at Google I/O.[26][27] The Samsung model was released on 15 June 2011, but the Acer was delayed until mid-July.[28][29] In August 2011, Netflix announced official support for Chrome OS through its streaming service, allowing Chromebooks to watch streaming movies and TV shows via Netflix. At the time, other devices had to use Microsoft Silverlight to play videos from Netflix.[30] Later in that same month, Citrix released a client application for Chrome OS, allowing Chromebooks to access Windows applications and desktops remotely.[31] Dublin City University became the first educational institution in Europe to provide Chromebooks for its students when it announced an agreement with Google in September 2011.[32]
Expansion[edit]
Samsung Chromebook
By 2012, demand for Chromebooks had begun to grow, and Google announced a new range of devices, designed and manufactured by Samsung. In so doing, they also released the first Chromebox, the Samsung Series 3, which was Chrome OS's entrance into the world of desktop computers.[33] Although they were faster than the previous range of devices, they were still underpowered compared to other desktops and laptops of the time, fitting in more closely with the Netbook market. Only months later, in October, Samsung and Google released a new Chromebook at a significantly lower price point ($250, compared to the previous Series 5 Chromebooks' $450).[34] It was the first Chromebook to use an ARM processor, one from Samsung's Exynos line. In order to reduce the price, Google and Samsung also reduced the memory and screen resolution of the device. An advantage of using the ARM processor, however, was that the Chromebook didn't require a fan. Acer followed quickly after with the C7 Chromebook, priced even lower ($199), but containing an Intel Celeron processor.[35] One notable way which Samsung reduced the cost of the C7 was to use a laptop hard disk rather than a solid state drive.
In April 2012, Google made the first update to Chrome OS's user interface since the operating system had launched, introducing a hardware-accelerated window manager called 'Aura' along with a conventional taskbar. The additions marked a departure from the operating system's original concept of a single browser with tabs and gave Chrome OS the look and feel of a more conventional desktop operating system. 'In a way, this almost feels as if Google is admitting defeat here', wrote Frederic Lardinois on TechCrunch. He argued that Google had traded its original version of simplicity for greater functionality. 'That’s not necessarily a bad thing, though, and may just help Chrome OS gain more mainstream acceptance as new users will surely find it to be a more familiar experience.'[36]Lenovo and HP followed Samsung and Acer in manufacturing Chromebooks in early 2013 with their own models.[37] Lenovo specifically targeted their Chromebook at students, headlining their press release with 'Lenovo Introduces Rugged ThinkPad Chromebook for Schools'.[38][39]
When Google released Google Drive, they also included Drive integration in the next version of Chrome OS (version 20), released in July 2012.[40] While Chrome OS had supported Flash since 2010,[41] by the end of 2012 it had been fully sandboxed, preventing issues with Flash from affecting other parts of Chrome OS.[42] This affected all versions of Chrome including Chrome OS.
Chromebook Pixel[edit]
Chromebook Pixel (WiFi) open
Silvercrest metals. Up to this point, Google had never made their own Chrome OS device. Instead, Chrome OS devices were much more similar to their Nexus line of Android phones, with each Chrome OS device being designed, manufactured, and marketed by third party manufacturers, but with Google controlling the software. However, in February 2013 this changed when Google released the Chromebook Pixel.[43] The Chromebook Pixel was a departure from previous devices. Not only was it entirely Google-branded, but it contained an Intel i5 processor, a high-resolution (2,560x1,700) touchscreen display, and came at a price point more competitive with business laptops.[44]
Controversial popularity[edit]
By the end of 2013, analysts were undecided on the future of Chrome OS. Although there had been articles predicting the demise of Chrome OS since 2009,[45][46][47][48][49] Chrome OS device sales continued to increase substantially year-over-year. In mid 2014, Time Magazine published an article titled 'Depending on Who's Counting, Chromebooks are Either an Enormous Hit or Totally Irrelevant', which detailed the differences in opinion.[50] This controversy was further spurred by the fact that Intel seemed to decide Chrome OS was a beneficial market for it, holding their own Chrome OS events where they announced new Intel-based Chromebooks, Chromeboxes, and an all-in-one from LG called the Chromebase.[51]
Seizing the opportunity created by the end of life for Windows XP, Google pushed hard to sell Chromebooks to businesses, offering significant discounts in early 2014.[52]
Pwnium competition[edit]
In March 2014, Google hosted a hacking contest aimed at computer security experts called 'Pwnium'. Similar to the Pwn2Own contest, they invited hackers from around the world to find exploits in Chrome OS, with prizes available for attacks. Two exploits were demonstrated there, and a third was demonstrated at that year's Pwn2Own competition. Google patched the issues within a week.[53]
Material Design and App Runtime for Chrome[edit]
Although the Google Native Client has been available on Chrome OS since 2010,[54] there originally were few Native Client apps available, and most Chrome OS apps were still web apps. However, in June 2014, Google announced at Google I/O that Chrome OS would both synchronise with Android phones to share notifications and begin to run Android apps, installed directly from the Google Play Store.[55] This, along with the broadening selection of Chromebooks,[56] provided an interesting future for Chrome OS.
At the same time, Google was also moving towards the then-new Material Design visual language for its products, which it would bring to its web products as well as Android Lollipop.[57] One of the first Material Design items to come to Chrome OS was a new default wallpaper,[58] though Google did release some screenshots of a Material Design experiment for Chrome OS that never made it into the stable version.[59]
Chromebox for Meetings[edit]
In an attempt to expand its enterprise offerings, Google released the Chromebox for Meetings in February 2014. The Chromebox for Meetings is a kit for conference rooms containing a Chromebox, a camera, a unit containing both a noise-cancelling microphone and speakers, and a remote control. It supports Google Hangouts meetings, Vidyo video conferences, and conference calls from UberConference.[60][61] Several partners announced Chromebox for Meetings models with Google, and in 2016 Google announced an all-in-one Chromebase for Meetings for smaller meeting rooms.[62]
Hardware[edit]
A Chromebook.
Laptops running Chrome OS are known collectively as 'Chromebooks'. The first was the CR-48, a reference hardware design that Google gave to testers and reviewers beginning in December 2010. Retail machines followed in May 2011. A year later, in May 2012, a desktop design marketed as a 'Chromebox' was released by Samsung. In March 2015 a partnership with AOPEN was announced and the first commercial Chromebox was developed.[63]
In early 2014, LG Electronics introduced the first device belonging to the new all-in-one form factor called 'Chromebase'. Chromebase devices are essentially Chromebox hardware inside a monitor with built-in camera, microphone and speakers.
The Chromebit is an HDMI dongle running Chrome OS. When placed in an HDMI slot on a television set or computer monitor, the device turns that display into a personal computer. The device was announced in March 2015 and shipped that November.[64]
Chrome OS supports dual-monitor setups, on devices with a video-out port.
Applications[edit]
Chrome OS running six different web browsers
How To Download Chromebook To Xp 2019 Free
Initially, Chrome OS was almost a pure web thin client operating system that relied primarily on servers to host web applications and related data storage.[65][66] Google gradually began encouraging developers to create 'packaged applications', and later, Chrome Apps. The latter employs HTML5, CSS, Adobe Shockwave, and JavaScript to provide a user experience closer to a native application.[67][68]
In September 2014, Google launched App Runtime for Chrome (beta), which allowed certain ported[69] Android applications to run on Chrome OS. Runtime was launched with four Android applications: Duolingo, Evernote, Sight Words, and Vine.[70] In 2016, Google made the Google Play Store available for Chrome OS, making most Android apps available for supported Chrome OS devices.[71]
Google announced in 2018 that Chrome OS would be getting support for desktop Linux apps.[72] This capability was released to the stable channel with Chrome 69 in October 2018, but was still marked as beta.[73]
Chrome Apps[edit]
Google has encouraged developers to build not just conventional Web applications for Chrome OS, but Chrome Apps (formerly known as Packaged apps). From a user perspective, Chrome Apps resemble conventional native applications: they can be launched outside of the Chrome browser, are offline by default, can manage multiple windows, and interact with other applications. Technologies employed include HTML5, JavaScript, and CSS.[74][75][76]
Integrated media player, file manager[edit]
Google integrates a media player into both Chrome OS and the Chrome browser, enabling users to play back MP3s, view JPEGs, and handle other multimedia files while offline.[77] It supports DRM videos.[78]
Chrome OS also includes an integrated file manager, resembling those found on other operating systems, with the ability to display directories and the files they contain from both Google Drive and local storage, as well as to preview and manage file contents using a variety of Web applications, including Google Docs and Box.[79] Since January 2015, Chrome OS can also integrate additional storage sources into the file manager, relying on installed extensions that use the File System Provider API.[80]
Remote application access and virtual desktop access[edit]
In June 2010, Google software engineer Gary Kačmarčík wrote that Chrome OS will access remote applications through a technology unofficially called 'Chromoting', which would resemble Microsoft's Remote Desktop Connection.[77] The name has since been changed to 'Chrome Remote Desktop', and is like 'running an application via Remote Desktop Services or by first connecting to a host machine by using RDP or VNC'.[81] Initial roll-outs of Chrome OS laptops (Chromebooks) indicate an interest in enabling users to access virtual desktops.[82][83]
Android applications[edit]
At Google I/O 2014, a proof of concept showing Android applications, including Flipboard, running on Chrome OS was presented. In September 2014, Google introduced a beta version of the App Runtime for Chrome (ARC), which allows selected Android applications to be used on Chrome OS, using a Native Client-based environment that provides the platforms necessary to run Android software. Android applications do not require any modifications to run on Chrome OS, but may be modified to better support a mouse and keyboard environment. At its introduction, Chrome OS support was only available for selected Android applications.[84]
In 2016, Google introduced the ability to run Android apps on supported Chrome OS devices, with access to the entire Google Play Store. The previous Native Client-based solution was dropped in favor of a container containing Android's frameworks and dependencies (initially based on Android Marshmallow), which allows Android apps to have direct access to the Chrome OS platform, and allow the OS to interact with Android contracts such as sharing. Engineering director Zelidrag Hornung explained that ARC had been scrapped due to its limitations, including its incompatibility with the Android Native Development Toolkit (NDK), and that it was unable to pass Google's own compatibility test suite.[85][86]
Linux Apps[edit]
Since 2013 it has been possible to run Linux applications in Chrome OS through the use of Crouton, a third-party set of scripts that allows access to a Linux distribution such as Ubuntu.[87] However, in 2018 Google announced that desktop Linux apps were officially coming to Chrome OS.[88] The main benefit claimed by Google of their official Linux application support is that it can run without enabling developer mode, keeping many of the security features of Chrome OS. It was noticed in the Chromium OS source code in early 2018.[89][90] Early parts of Crostini were made available for the Google Pixelbook via the dev channel in February 2018 as part of Chrome OS version 66,[91][92] and it was enabled by default via the beta channel for testing on a variety of chromebooks in August 2018 with version 69.[93]
Architecture[edit]
Google's project for supporting Linux applications in Chrome OS is called Crostini, named for the Italian bread-based starter, and as a pun on Crouton. Crostini runs a virtual machine through a virtual machine monitor called crosvm, which uses Linux's built-in KVM virtualization tool. Although crosvm supports multiple virtual machines, the one used for running Linux apps, Termina, contains a basic Chrome OS kernel and userland utilities, in which it runs containers based on Linux containers (specifically LXD).[94]
Architecture[edit]
Chrome OS is built on top of the Linux kernel. Originally based on Ubuntu, its base was changed to Gentoo Linux in February 2010.[95] In preliminary design documents for the Chromium OS open source project, Google described a three-tier architecture: firmware, browser and window manager, and system-level software and userland services.[96]
Security[edit]
In March 2010, Google software security engineer Will Drewry discussed Chrome OS security. Drewry described Chrome OS as a 'hardened' operating system featuring auto-updating and sandbox features that will reduce malware exposure. He said that Chrome OS netbooks will be shipped with Trusted Platform Module (TPM), and include both a 'trusted bootpath' and a physical switch under the battery compartment that actuates a developer mode. That mode drops some specialized security functions but increases developer flexibility. Drewry also emphasized that the open source nature of the operating system will contribute greatly to its security by allowing constant developer feedback.[97]
At a December 2010 press conference, Google claimed that Chrome OS would be the most secure consumer operating system due in part to a verified boot ability, in which the initial boot code, stored in read-only memory, checks for system compromises.[98]
Shell access[edit]
Chrome OS includes the Chrome Shell, or 'crosh',[99] which documents minimal functionality such as ping and SSH at crosh start-up.
In developer mode, a full-featured bash[100] shell (which is supposed to be used for development purposes[101]) can be opened via VT-2, and is also accessible using the crosh command
shell .[102] To access full privileges in shell (e.g. sudo) a root password is requested. For some time the default was 'chronos' in Chrome OS and 'facepunch' in Chrome OS Vanilla[103] and later the default was empty, and instructions on updating it were displayed at each login.
Open source[edit]
Chrome OS is partially developed under the open sourceChromium OS project.[104] As with other open source projects, developers can modify the code from Chromium OS and build their own versions, whereas Chrome OS code is only supported by Google and its partners and only runs on hardware designed for the purpose. Unlike Chromium OS, Chrome OS is automatically updated to the latest version.[16]
Chrome OS on Windows[edit]
On Windows 8 exceptions allow the default desktop web browser to offer a variant that can run inside its full-screen 'Metro' shell and access features such as the Share charm, without necessarily needing to be written with Windows Runtime. Chrome's 'Windows 8 mode' was previously a tablet-optimized version of the standard Chrome interface. In October 2013, the mode was changed on Developer channel to offer a variant of the Chrome OS desktop.[105][106][107][108][109]
Design[edit]
Early in the project, Google provided publicly many details of the Chrome OS's design goals and direction,[110] although the company has not followed up with a technical description of the completed operating system.
User interface[edit]
Old Chrome-Chromium OS login screen
Design goals for Chrome OS's user interface included using minimal screen space by combining applications and standard Web pages into a single tab strip, rather than separating the two. Designers considered a reduced window management scheme that would operate only in full-screen mode. Secondary tasks would be handled with 'panels': floating windows that dock to the bottom of the screen for tasks like chat and music players. Split screens were also under consideration for viewing two pieces of content side-by-side. Chrome OS would follow the Chrome browser's practice of leveraging HTML5's offline modes, background processing, and notifications. Designers proposed using search and pinned tabs as a way to quickly locate and access applications.[111]
New window manager and graphics engine[edit]
On April 10, 2012, a new build of Chrome OS offered a choice between the original full-screen window interface and overlapping, re-sizable windows, such as found on Microsoft Windows and Apple's macOS. The feature was implemented through the Ash window manager, which runs atop the Aura hardware-accelerated graphics engine. The April 2012 upgrade also included the ability to display smaller, overlapping browser windows, each with its own translucent tabs, browser tabs that can be 'torn' and dragged to new positions or merged with another tab strip, and a mouse-enabled shortcut list across the bottom of the screen. One icon on the task bar shows a list of installed applications and bookmarks. Writing in CNET, Stephen Shankland argued that with overlapping windows, 'Google is anchoring itself into the past' as both iOS and Microsoft's Metro interface are largely or entirely full-screen. Even so, 'Chrome OS already is different enough that it's best to preserve any familiarity that can be preserved'.[112][113][114]
Printing[edit]
Google Cloud Print is a Google service that helps any application on any device to print on supported printers. While the cloud provides virtually any connected device with information access, the task of 'developing and maintaining print subsystems for every combination of hardware and operating system—from desktops to netbooks to mobile devices—simply isn't feasible.'[115][116] The cloud service requires installation of a piece of software called proxy, as part of the Chrome OS. The proxy registers the printer with the service, manages the print jobs, provides the printer driver functionality, and gives status alerts for each job.[117]
In 2016, Google included 'Native CUPS Support' in Chrome OS as an experimental feature that may eventually become an official feature. With CUPS support turned on, it becomes possible to use most USB printers even if they do not support Google Cloud Print.[118][119]
Link handling[edit]
Chrome OS was designed with the intention of storing user documents and files on remote servers. Both Chrome OS and the Chrome browser may introduce difficulties to end users when handling specific file types offline; for example, when opening an image or document residing on a local storage device, it may be unclear whether and which specific Web application should be automatically opened for viewing, or the handling should be performed by a traditional application acting as a preview utility. Matthew Papakipos, Chrome OS engineering director, noted in 2010 that Windows developers have faced the same fundamental problem: 'Quicktime is fighting with Windows Media Player, which is fighting with Chrome.'[13]
Release channels and updates[edit]
Chrome OS uses the same release system as Google Chrome: there are three distinct channels: Stable, Beta, and Developer preview (called the 'Dev' channel). The stable channel is updated with features and fixes that have been thoroughly tested in the Beta channel, and the Beta channel is updated approximately once a month with stable and complete features from the Developer channel. New ideas get tested in the Developer channel, which can be very unstable at times.[120][121] A fourth canary channel was confirmed to exist by Google Developer Francois Beaufort and hacker Kenny Strawn, by entering the Chrome OS shell in developer mode, typing the command shell to access the bash shell, and finally entering the command update_engine_client -channel canary-channel -update. It is possible to return to verified boot mode after entering the canary channel, but the channel updater disappears and the only way to return to another channel is using the 'powerwash' factory reset.[122]
Reception[edit]
At its debut, Chrome OS was viewed as a competitor to Microsoft, both directly to Microsoft Windows and indirectly the company's word processing and spreadsheet applications—the latter through Chrome OS's reliance on cloud computing.[123][124] But Chrome OS engineering director Matthew Papakipos argued that the two operating systems would not fully overlap in functionality because Chrome OS is intended for netbooks, which lack the computational power to run a resource-intensive program like Adobe Photoshop.[13]
Some observers claimed that other operating systems already filled the niche that Chrome OS was aiming for, with the added advantage of supporting native applications in addition to a browser. Tony Bradley of PC World wrote in November 2009:
After this 2009 statement Chrome browser rose to become the number one browser used worldwide.[126]
By 2016, Chromebooks had become the most popular computer in the US K–12 education market.[127]
Relationship to Android[edit]
Google's offering of two open source operating systems, Android[128] and Chrome OS, has drawn some criticism despite the similarity between this situation and that of Apple Inc's two operating systems, macOS and iOS. Steve Ballmer, Microsoft CEO at the time, accused Google of not being able to make up its mind.[129]Steven Levy wrote that 'the dissonance between the two systems was apparent' at Google I/O 2011. The event featured a daily press conference in which each team leader, Android's Andy Rubin and Chrome's Sundar Pichai, 'unconvincingly tried to explain why the systems weren't competitive.'[130] Google co-founder Sergey Brin addressed the question by saying that owning two promising operating systems was 'a problem that most companies would love to face'.[130] Brin suggested that the two operating systems 'will likely converge over time.'[131] The speculation over convergence increased in March 2013 when Chrome OS chief Pichai replaced Rubin as the senior vice president in charge of Android, thereby putting Pichai in charge of both.[132]
The relationship between Android and Chrome OS became more substantial at Google I/O 2014, where developers demonstrated native Android software running on Chrome OS through a Native Client based runtime.[84][133] In October 2015, The Wall Street Journal reported that Chrome OS would be folded into Android so that a single OS would result by 2017. The resulting OS will be Android, but it will be expanded to run on laptops.[134][135] Google responded that while the company has 'been working on ways to bring together the best of both operating systems, there's no plan to phase out Chrome OS.'[136]
Notes[edit]See also[edit]
References[edit]
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Chrome_OS&oldid=904472332'
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |