Windows 7 Embedded Standard 32-bit went out of support in October 10th, 2023 as part of Security Updates Year 3, which means there is no more security updates. Any vulnerabilities that exist today will not be patched. You can see a list of reported vulnerabilities here.
We recommend Windows 10 IoT Enterprise LTSC 2019, which ends support on January 9th, 2029, or upgrading the image to Windows 10 IoT Enterprise LTSC 2021, which ends support on January 13th, 2032.
For extended support, you can upgrade to Windows 11 IoT Enterprise LTSC 2024, which ends support on October 10th, 2034, but requires activation through Microsoft Activation Scripts (MAS) or else after evaluation expires (90 days), the kiosk will shut down after 2 hours.
Some tinkerers have noted installing an older style GPU with no power connectors has resolved this issue and has improved CPU usage on Windows 10/11 IoT Enterprise LTSC. You can pick up a cheap one on eBay or Amazon as long as it supports 1GB or better. Make sure it includes a VGA cable and editing the Display Resolution is required after installing the appropriate drivers from the manufacturers.
Some kiosks come configured with their GPU drivers disabled. This results in the user interface being exceptionally slow and choppy. Animations will stutter and tear, and overall it looks quite bad.
You can attempt to fix this by simply turning on the GPU drivers in Device Manager, accessible via Redbox Desktop. Techs have noted that this may not work and the device will simply not boot until you enter safe mode, though this doesn't appear to strictly be the case, and is worth trying.
One potential route is using a DisplayPort to DVI cable or adapter and re-running the cable through the harness to the door if your VGA cable doesn't work. Note that Windows will take forever to boot the first time you do this, so give it 10-20 minutes before you give up and reset everything. It will seem like it's frozen, but it's not. If your disk activity light is out and the keyboard isn't responding, something may have went wrong.
Kiosks have been reported to have issues where the titles in the engine disappear. The cause for this is due to a dead CMOS battery on reboot. Without an active internet connection, the time and dates will not update and will require replacing the CMOS battery and setting the date and time manually in BIOS Setup (follow your PC's guide to get to the correct settings). If this is still occurring, following the steps below, which should fix the issue also.
C:\Program Files\REDS\KioskEngine\Data\profile.dataMost cellular modems come with Verizon 4G LTE plans, a limited amount instead have T-Mobile plans. Over time, these SIM cards may become inactive or have already stopped working, rendering the cellular modem unusable. To restore functionality, you will need to replace the inactive SIM card with either an active one or a SIM card compatible with Verizon.
You have the following options:
However, you may not want to expose your computer to the internet as it may cause complications in the future when software is no longer supported (or in case of being required to upgrade Windows 7). But, if you're planning on enabling SMB or installing your own VNC Server to access your kiosk over the internet, you'll have to connect it. To prevent any complications, you can setup Firewall Rules to expose certain ports for the computer, and restrict other hostnames (or, you can reject requests made from LAN -> WAN to keep it available local-only).
Ensure that the kiosk is positioned upright and completely level. Use a spirit level or similar tool to confirm it is not tilted in any direction. If the kiosk is leaning or uneven, adjust the leveling feet at the bottom to achieve proper alignment. Rotate the feet as needed to stabilize the kiosk and ensure it stands precisely at a 90-degree angle relative to the floor or base surface. Double-check the alignment and stability after adjustments to confirm it is secure and correctly positioned.
bootrec /fixmbr and bootrec /rebuildbcd.If none of the above steps resolve your issue, you may need to replace the storage drive. Replacing the old drive with a HDD (not recommended) or SSD (recommended) is advised. This is common with older kiosks, as many of the hard drives are either nearing failure or have already failed.
This issue is common in the Premio M2H6V1 computer when upgrading from Windows 7 Embedded 32bit. Here is how to solve that issue:
Delete) during startup.Advanced tab using arrow keys.Windows 8 Mode.Enter, and make sure its enabled.F10 to save changes and restart the PC.Shell, then you will need to verify the drive partitions are correct and not corrupted.Following could cause this issue:
The disc was likely “thinned” by Redbox or purchased and later returned. Any discs left in the carousel are moved to the drop bin during Inventory Sort Mondays. The only way to relink a barcode to a title is to add that barcode back into the database for that specific title. You can use Viper’s Title Manager (available in the official Discord) to link a barcode to a title. When discs are thinned or sold, their barcodes are reported to Redbox’s servers and pushed to all kiosks in Update Manager patches, which removes those barcodes from the database.
This is likely as the Kiosk was decommissioned and was set for removal. Kiosks decommissioned around June of 2023 were still left at the store due to delinquent payments to vendors, like Brendamour Logistics, which caused these kiosks to remain at the retailers even up to the bankruptcy in 2024. You can commonly find these at current/former 7-11 and current/former Winn Dixie kiosks.
You can use about any PC in the kiosk as long as it has a Serial Port. You could source a USB/PCIE adapter, but we recommend on board to prevent sudden disconnection as if the Y motor goes down or up could cause spikes and could damage the gripper components. Consumer motherboards/computers have not had this port included since 2004, but business motherboards/computers still include these ports.
The card reader, you would need to source one for another kiosk or use a patched dll to simulate the card reader.