UPDATE: A Window's time problem has been corrected as described below.I bought this Beelink Mini system to replace a pair of “hulking” desktop systems running Windows 10 and MX Linux 21. After working around a few problems - see below - this system is fulfilling my needs and should allow me to unload the old desktop systems and free up a lot of desk space! I hope that this review will be helpful to potential purchasers of this or similar Beelink systems.Since the Beelink system came with the Professional version of Windows 11 it was easy to configure the system with a Local rather than a Microsoft account. It took some time to update Windows to release 22H2, but there were no problems in doing so. I was glad to see that no “bloatware” was included in Beelink’s copy of Windows 11.The only problem I found initially was with the time setting. Every time I logged into Windows the time was wrong by a certain number of hours (the minutes were correct) even though the time zone was set correctly! The problem, apparently, is that Linux by default uses UTC time. Windows, on the other hand, maintains its clock in local time. It is this conflict that results in Windows showing an incorrect time. One solution to this problem is to modify Linux so it uses local time rather than UTC time. The details for making this modification vary from one Linux distro to another, but below is the approach I used with MX Linux. (These steps are also shown in two attached screenshots.)===============================--> Run the "MX Date & Time" app.--> Click on the "Date & Time" tab and verify that the proper time zone has been set. If not, use the drop down lists to choose the correct country and city.--> Now click on "Hardware Clock". Make sure the "local" option is selected for "Time zone for the Hardware Clock". Then, under "Time transfer", click on "Hardware Clock to System Clock." Now verify in the listing (shown lower down in the same window) that "Hardware clock is on local time".--> Assuming that all settings appear to be correct, click on the "Apply" button.--> The "MX Date and Time" window can now be closed.The Windows and Linux times should now be correctly displayed.===============================I’m mainly using MX Linux 21.3 rather than Windows, so I added a 512GB SSD to the Beelink system and installed Linux on that disk. There was no problem doing this, but great care must be taken when removing the bottom cover of the Beelink system to avoid damaging the thin cable used to connect the SSD.Once the new SSD was installed I was able to use the Live USB feature of MX Linux to move the system that was on the old desktop system over to the new Beelink. With Windows on the built-in SSD and Linux on the added SSD it is possible to boot either system. (I mainly use Linux, so I modified the “boot” order to start that system by default.)This move went smoothly and only two item required updating on the new MX Linux system:--> The driver for a separately-puchased USB WiFi adapter needed to reinstalled. (The WiFi card in the Beelink is not currently supported under Linux. Once the driver was installed, the WiFi adapter was recognized and my download speed of 195Mbps is about the best possible from my ISP.)--> The Suspend option under MX Linux 21.3 does not work - the system appears to suspend, but it cannot be “woken up”. (Actually, the system may be waking up, but the monitor remains OFF.) To get around this problem I’m using the command: echo freeze | tee /sys/power/stateto turn off all I/O and “freeze” the system RAM. I understand that this approach does not conserve as much power as “Suspend to RAM”, but it is the only Suspend option that seems to work!Once the system was operating correctly with both Windows 11 and MX Linux 21.3, I added an external 2TB SSD (via USB 3) to hold system backups. This external disk has two partitions, one formatted as EXT4 (for Linux) and one formatted as NTFS (for Windows). For Linux I’m using Timeshift to back up the operating system, Backups (i.e. DejaDup) to back up user files, and MX Live USB maker to back up the entire system. NOTE: As an alternative, when running Windows, it is possible to run Macrium Reflect and completely back up the entire Linux disk.I have noticed that the system runs quite “hot” when heavily loaded. For example, the MX Snapshot app uses 100% of available CPU time on all four CPU cores which causes the core temperatures to reach around 95 deg C. I’m not sure if this is causing the CPU to be “throttled”, but such a high temperature can’t be great for either the CPU or other system components. To alleviate this problem (at least to some extent) I purchase two small 40mm x 40mm USB-powered fans and attached them to the sides of the Beelink case (making sure that they are blowing air INTO the case). Running these fans seems to significant reduce the CPU temperatures, although more testing must be done to determine the exact amount of improvement.Be aware that power is maintained on the Beelink USB ports even when the system is powered down! As a consequence, the above mentioned fans will run continuously. Although not too noisy, I wanted a way to turn them off when they are not needed. My solution was to use a 4-port USB hub with push-button switches that can be used to turn the USB power on or off as required. (I’m using a USB 2 hub that I had “lying around”, but I may replace it with a USB 3 hub that will control the fans as well as several other USB devices that I have connected to the Beelink system.) Please see attached picture to see how the fans are attached to the system.