The diskless vs hybrid choice looks bigger than it is. Both modes manage the same Windows image from the same server. Both keep one game library for the whole floor. Both put a seat back to a clean state when it restarts. The single thing that differs is where each PC loads Windows from: over the network, or from a copy of the image on its own SSD.
And you don't have to answer it once for the whole room. You answer it per PC.
What the two modes have in common
Start here, because most of the confusion comes from assuming these are two products with two ways of working. They aren't.
In both modes there is one image on the server, and that image is the only Windows install you maintain. When you want to change it, to add a driver or a launcher or a Windows update, you switch one PC into Super Client, make the change there, and save it back. The image keeps versions, so each saved change is a point you can return to.
In both modes a seat that isn't in Super Client is disposable. Whatever a customer installs or breaks during a session is reverted at the next reboot, and the PC comes back in its previous clean state.
In both modes the games and shared data live on the server and are managed there. One copy of each game, patched once.
Think about what that means on patch day. A big shooter drops an update on a Tuesday. You update the game once, on the server, and every seat in the room has the new version the next time it starts. It makes no difference whether seat 9 is a diskless PC and seat 10 is a hybrid one, because neither of them stores the game. On the question owners care about most, how many times do I have to install this patch, diskless vs hybrid has the same answer: once.
That's the whole operating model of CCBoot, and it's identical on either side of this comparison. If you've been reading hybrid as "diskless with something missing", set that aside. Nothing in the list above is missing from it.
The one real difference
It comes down to the first thirty seconds after the power button.
A diskless seat has no drive in it. It starts from the network, finds the server, and loads Windows straight from the image the server holds. The image never leaves the server. The client is a motherboard, a graphics card, memory and a network port.
A hybrid seat has an SSD, and that SSD holds a VHD created from the server's image. The PC boots Windows directly from that local VHD. Once it's up, it reaches the server for the same things a diskless seat does: the games, the shared data, and the management that keeps it in line with every other PC.
So in both modes the image is the server's image. In one the seat reads it across the wire. In the other the seat carries a copy.
A customer can't tell which one they're sitting at. The desktop is the one you built and the game menu lists the same games (both come from the server, so it would be strange if they differed). Staff can't tell from the front of the PC either. The only place the difference is visible is the admin panel, in one field on each computer's record.
Diagram of a diskless seat booting from the network and a hybrid seat booting from a local VHD, both served by one server
What each kind of seat needs
For a diskless seat, the list is short. No drive. A BIOS set to boot from the network first. One image fits clients with different hardware, so a floor with three generations of motherboard still runs from a single image.
For a hybrid seat, the requirement is the thing most US gaming PCs already ship with: an SSD or NVMe drive in the machine. The setup has two parts, both done once.
On the server, hybrid is a setting. Open Settings, go to Center settings, and in the diskless mode option choose Hybrid. Then on the Disks page you tell it which disk holds the image and set up the write-back disk and the game disk.
On the client, a small tool called CCBootUSB writes the image to the PC's drive as a VHD. You can install to the SSD directly, or build a bootable USB drive first and carry it down the row, which is the practical way to do 30 machines. (Use a fast USB drive for that. The guidance is read and write speeds of at least 300 MB/s, and you'll feel the difference by the fifth PC.) When it finishes, the SSD has a 100GB C: drive and the rest of its space set aside as a data partition.
Which SSDs are worth buying shifts every few months, so if any of your seats need a drive, ask support which drives they're recommending right now instead of trusting a model number in an article.
Updating the image works the same way
This is the part people expect to be different, and it's the part that's most alike.
You pick one PC and enable Super Client for it. The PC restarts into an editable state. You do whatever the update is: install the new launcher, add the anti-cheat component, apply the Windows patch. When you're finished, you turn Super Client off and tell the system to keep what you did. On a diskless seat that's the Update the Image option, with a short note describing the change. On a hybrid seat it's Keep the Changes.
The hybrid save has one behavior worth knowing in advance, so leave the machine alone while it happens. It reboots by itself and shows a loading percentage, and it shows it twice, because the changes are being copied into the image in two stages. Both passes have to be finished. The mistake almost everyone makes the first time is watching the counter reach the end, seeing it start again from zero, deciding it has hung, and pulling the power. It hasn't hung. Let the second pass run.
When it's done, the version list shows a new entry. The original image is V0, your first update is V1, the next is V2, and so on.
Those versions are what make updates low-stakes. If V3 turns out to have a problem, say a driver that misbehaves on one group of PCs, you open the image list, pick the version you trust, and restore it. No rebuilding. Once a set of updates has been running cleanly for a while and you're sure of it, Merge All folds the restore points into the main image and tidies the list. Merge when you're confident, since the point of keeping versions is having them when you want them.
Put the two side by side and the routine is one routine: one PC, one edit, one save, a new version on the server. In practice, whoever learns it on a diskless seat can do it on a hybrid seat the same afternoon. For a room with one person on shift that's the real answer to diskless vs hybrid, since there's only one procedure to train and only one checklist taped next to the server.
Do you have to pick one for the whole floor?
No, and this is the most useful thing to know about diskless vs hybrid.
The choice is a property of each PC, not of the server. On the Images page the server lists two kinds of image side by side: local SSD images and PXE images. Then, for any PC, you open Computers, select the machine, click Edit PC, and set its Image field. Choose Local and that seat boots from its own SSD. Choose one of the PXE images and it boots from the network.
The Edit PC dialog in the admin panel, where the Image field decides how that seat boots
PC1 can boot locally while PC2 boots from a PXE image, on the same server, in the same room, in the same minute. Both are managed from the same panel.
One practical note if you ever move a seat from local boot to network boot: change the boot priority in that PC's BIOS so it tries the network first. The server setting tells the PC what it should do. The BIOS decides what it tries. The wiki walks through the mixed setup on the page on running Hybrid and PXE together.
Here's why this matters for the way US rooms are built. A gaming center rarely buys every PC on the same day. You open with 30 machines that came with NVMe drives, because that's how gaming PCs are sold. Eighteen months later you add 20 seats, and this time you can order them without drives and put that line of the budget into better graphics cards. With per-PC selection those two purchases don't force two systems on you. The first 30 run hybrid on the drives they came with, the new 20 run diskless, and a game patch is still one job on one server.
Diskless vs hybrid at a glance
| Diskless | Hybrid |
Windows boots from | The network, loading the | A VHD of that image on |
Drive in the client | None | SSD or NVMe |
Image maintained | One, on the server | One, on the server |
How you change it | Super Client on one PC, | Super Client on one PC, |
Image versions | Restore points you can | V0, V1, V2, with Restore |
After a reboot | Seat returns to its clean | Seat returns to its clean |
Games and shared data | On the server | On the server |
Chosen | Per PC, by its Image | Per PC, by its Image |
Six of those eight rows say the same thing twice. That's the point of the table.
Which seats get which
Sort the PCs, not the room.
Machines you haven't bought yet, or machines with no drive in them, are diskless seats. There's nothing to install on them and nothing in them to wear out, and the money that would have gone to 20 or 40 drives is free for parts a customer will notice.
Machines that already have an SSD or NVMe drive are hybrid seats. The drive is paid for and it's good at what it does, so let it carry the local copy of the image. You get the single managed image, the versions and the clean reboot without opening a case.
Honestly, most rooms end up with some of each, and that's a fine place to be. The grouping usually follows the purchase orders: this row came with drives, that row didn't.
The grouping isn't permanent either. A seat can change sides later with the same Image field you used to set it up. Say a hybrid PC's drive reaches the end of its life three years in. You don't have to replace the drive to keep the seat. Point that PC at a PXE image, set its BIOS to boot from the network, and it carries on as a diskless seat on the same server, with the same games, on the same afternoon (the customer who sits there next won't know anything happened).
Licensing is counted by client PC in both modes, so the mix you choose doesn't change how you count seats. You can check the current per-PC pricing against your total.
Two rows of gaming PCs in a LAN center with players seen from behind
Try both on one bench
You can settle this without touching the floor. Take one server and two spare PCs, one with an SSD and one with its drive pulled.
Download the trial, build an image, and point the first PC at Local and the second at a PXE image. Boot them next to each other. Then do one Super Client update on the hybrid PC, something small like installing a single app, choose Keep the Changes, wait out both loading passes, and look at the version list.
At that point you've seen everything in this article with your own hands: two boot paths, one server, one game library, and an update saved as a version. The diskless vs hybrid question stops being a decision about your whole business and becomes a dropdown you set for each seat.
Diagram of a diskless seat booting from the network and a hybrid seat booting from a local VHD, both served by one server
What each kind of seat needs
For a diskless seat, the list is short. No drive. A BIOS set to boot from the network first. One image fits clients with different hardware, so a floor with three generations of motherboard still runs from a single image.
For a hybrid seat, the requirement is the thing most US gaming PCs already ship with: an SSD or NVMe drive in the machine. The setup has two parts, both done once.
On the server, hybrid is a setting. Open Settings, go to Center settings, and in the diskless mode option choose Hybrid. Then on the Disks page you tell it which disk holds the image and set up the write-back disk and the game disk.
On the client, a small tool called CCBootUSB writes the image to the PC's drive as a VHD. You can install the SSD directly, or build a bootable USB drive first and carry it down the row, which is the practical way to do 30 machines. (Use a fast USB drive for that. The guidance is read and write speeds of at least 300 MB/s, and you'll feel the difference by the fifth PC.) When it finishes, the SSD has a 100GB C: drive and the rest of its space set aside as a data partition.
Which SSDs are worth buying shifts every few months, so if any of your seats need a drive, ask support which drives they're recommending right now instead of trusting a model number in an article.
Updating the image works the same way
This is the part people expect to be different, and it's the part that's most alike.
You pick one PC and enable Super Client for it. The PC restarts into an editable state. You do whatever the update is: install the new launcher, add the anti-cheat component, apply the Windows patch. When you're finished, you turn Super Client off and tell the system to keep what you did. On a diskless seat that's the Update the Image option, with a short note describing the change. On a hybrid seat it's Keep the Changes.
The hybrid save has one behavior worth knowing in advance, so leave the machine alone while it happens. It reboots by itself and shows a loading percentage, and it shows it twice, because the changes are being copied into the image in two stages. Both passes have to be finished. The mistake almost everyone makes the first time is watching the counter reach the end, seeing it start again from zero, deciding it has hung, and pulling the power. It hasn't hung. Let the second pass run.
When it's done, the version list shows a new entry. The original image is V0, your first update is V1, the next is V2, and so on.
Those versions are what make updates low-stakes. If V3 turns out to have a problem, say a driver that misbehaves on one group of PCs, you open the image list, pick the version you trust, and restore it. No rebuilding. Once a set of updates has been running cleanly for a while and you're sure of it, Merge All folds the restore points into the main image and tidies the list. Merge when you're confident, since the point of keeping versions is having them when you want them.
Put the two side by side and the routine is one routine: one PC, one edit, one save, a new version on the server. In practice, whoever learns it on a diskless seat can do it on a hybrid seat the same afternoon. For a room with one person on shift that's the real answer to diskless vs hybrid, since there's only one procedure to train and only one checklist taped next to the server.
Do you have to pick one for the whole floor?
No, and this is the most useful thing to know about diskless vs hybrid.
The choice is a property of each PC, not of the server. On the Images page the server lists two kinds of image side by side: local SSD images and PXE images. Then, for any PC, you open Computers, select the machine, click Edit PC, and set its Image field. Choose Local and that seat boots from its own SSD. Choose one of the PXE images and it boots from the network.
The Edit PC dialog in the admin panel, where the Image field decides how that seat boots
PC1 can boot locally while PC2 boots from a PXE image, on the same server, in the same room, in the same minute. Both are managed from the same panel.
One practical note if you ever move a seat from local boot to network boot: change the boot priority in that PC's BIOS so it tries the network first. The server setting tells the PC what it should do. The BIOS decides what it tries. The wiki walks through the mixed setup on the page on running Hybrid and PXE together.
Here's why this matters for the way US rooms are built. A gaming center rarely buys every PC on the same day. You open with 30 machines that came with NVMe drives, because that's how gaming PCs are sold. Eighteen months later you add 20 seats, and this time you can order them without drives and put that line of the budget into better graphics cards. With per-PC selection those two purchases don't force two systems on you. The first 30 run hybrid on the drives they came with, the new 20 run diskless, and a game patch is still one job on one server.
Diskless vs hybrid at a glance
| Diskless | Hybrid |
Windows boots from | The network, loading the image on the server | A VHD of that image on the PC's own SSD |
Drive in the client | None | SSD or NVMe |
Image maintained | One, on the server | One, on the server |
How you change it | Super Client on one PC, then save | Super Client on one PC, then Keep the Changes |
Image versions | Restore points you can return to | V0, V1, V2, with Restore and Merge All |
After a reboot | Seat returns to its clean state | Seat returns to its clean state |
Games and shared data | On the server | On the server |
Chosen | Per PC, by its Image setting | Per PC, by its Image setting |
Six of those eight rows say the same thing twice. That's the point of the table.
Which seats get which
Sort the PCs, not the room.
Machines you haven't bought yet, or machines with no drive in them, are diskless seats. There's nothing to install on them and nothing in them to wear out, and the money that would have gone to 20 or 40 drives is free for parts a customer will notice.
Machines that already have an SSD or NVMe drive are hybrid seats. The drive is paid for and it's good at what it does, so let it carry the local copy of the image. You get the single managed image, the versions and the clean reboot without opening a case.
Honestly, most rooms end up with some of each, and that's a fine place to be. The grouping usually follows the purchase orders: this row came with drives, that row didn't.
The grouping isn't permanent either. A seat can change sides later with the same Image field you used to set it up. Say a hybrid PC's drive reaches the end of its life three years in. You don't have to replace the drive to keep the seat. Point that PC at a PXE image, set its BIOS to boot from the network, and it carries on as a diskless seat on the same server, with the same games, on the same afternoon (the customer who sits there next won't know anything happened).
Licensing is counted by client PC in both modes, so the mix you choose doesn't change how you count seats. You can check the current per-PC pricing against your total.
Two rows of gaming PCs in a LAN center with players seen from behind
Try both on one bench
You can settle this without touching the floor. Take one server and two spare PCs, one with an SSD and one with its drive pulled.
Download the trial, build an image, and point the first PC at Local and the second at a PXE image. Boot them next to each other. Then do one Super Client update on the hybrid PC, something small like installing a single app, choose Keep the Changes, wait out both loading passes, and look at the version list.
At that point you've seen everything in this article with your own hands: two boot paths, one server, one game library, and an update saved as a version. The diskless vs hybrid question stops being a decision about your whole business and becomes a dropdown you set for each seat.




