<?xml version="1.0" encoding="UTF-8" ?>
  <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>My Portfolio</title>
        <link>https://rrrainielll.com</link>
        <description>This is my portfolio RSS feed</description>
        <item>
          <title>How I Installed Windows 11 on an Unsupported MacBook Using Boot Camp</title>
          <link>https://rrrainielll.com/blog/install-windows-11-on-unsupported-macbook-boot-camp</link>
          <description>Install Windows 11 on an unsupported Intel MacBook with Boot Camp using a simple Windows 10 upgrade trick.</description>
          <content:encoded><![CDATA[I got my first MacBook (MacBookPro 16,3) from Facebook Marketplace for **₱20,000** (around **$339.17**). This is my first time owning a MacBook, but I’m not entirely new to the Apple ecosystem—I’ve experimented with Hackintosh before.

That said, I’m still very much a Windows user. A lot of the apps I rely on aren’t fully compatible with macOS, so my only real option was to use **Boot Camp**. Unfortunately, when I tried installing Windows 11 directly using a Windows 11 ISO, I kept running into errors.

It was frustrating, so I settled for installing **Windows 10** first. But since I really needed Windows 11, I looked for a workaround—and thankfully, I found one.

---

## Prerequisites

- **Windows 10 ISO**
    
    https://www.microsoft.com/en-us/software-download/windows10ISO
    
- **Windows 11 ISO**
    
    https://www.microsoft.com/en-us/software-download/windows11
    

---

## Installation Guide

### 1. Install Windows 10 using Boot Camp

Download the **Windows 10 ISO** from the official Microsoft website and install it using **Boot Camp Assistant** on macOS.

If you’re only seeing the *Media Creation Tool* instead of the ISO:

- Press **F12** to open Developer Tools
- Click **Toggle Device Toolbar** (mobile view)
- Refresh the page
- You should now be able to download the ISO directly

---

### 2. Follow the Boot Camp instructions

Boot Camp Assistant will guide you through the setup and automatically install Windows 10.

Make sure you select **Windows 10** when prompted.

---

### 3. Complete the Windows 10 setup

Proceed like a normal Windows installation:

- Choose your region and keyboard
- Sign in or create an account
- Expect a few restarts during setup

---

### 4. Install Boot Camp drivers on Windows 10

Once Windows 10 is fully installed, install **Boot Camp Assistant** on Windows.

This ensures all Apple-specific drivers (keyboard, trackpad, audio, etc.) work properly.

Updating Windows 10 at this stage is optional.

---

### 5. Download and mount the Windows 11 ISO

Download the Windows 11 ISO and **mount it**.

Once mounted, it will appear as a drive under **This PC** (e.g., `E:`).


---

### 6. Open Command Prompt as Administrator

- Press **Win + R**
- Type `cmd`
- Hold **Ctrl + Shift**, then press **Enter** to run as administrator

Navigate to the mounted ISO drive by typing, for example:

```
E:
```

---

### 7. Upgrade to Windows 11

Run the following command:

```
setup.exe /product server
```

It looks confusing at first (and yes, I was confused too), but no—you’re **not** installing Windows Server. This simply bypasses the hardware checks and installs **Windows 11 Pro**.

![](https://raw.githubusercontent.com/rrrainielll/Blackout-Assets/refs/heads/main/posts/BootCamp%20windows%2011%20Installation/BootCamp%20windows%2011%20Installation.jpg)

Follow the on-screen instructions. Your MacBook will reboot automatically once the upgrade is complete.

⚠️ **Important reminders:**

- Do **not** force restart
- Make sure your MacBook is **plugged in**
- Installation time may vary depending on your hardware

Once done—congrats! You’re now on **Windows 11** 🎉

---

## Post-Installation (Important)

### 8. Reinstall Boot Camp drivers

Some drivers may break after upgrading.

- Open **Disk Management**
- Assign a drive letter to the **OSXRESERVED (10GB)** partition
- Open that partition and locate the **BootCamp** folder
- Copy the **BootCamp** folder and the related Windows dependency folder (you’ll recognize it)
- Run `setup.exe` inside the BootCamp folder

This will reinstall the necessary drivers.

---

### 9. Update Windows

Go to **Settings → Windows Update** and install all available updates.

This may take some time depending on your internet speed and hardware.

---

And that’s it.

Enjoy running **Windows 11 on your MacBook via Boot Camp**! 👌

---

If you encounter any issues please feel free to leave a comment in reddit post:

<SocialEmbed url="https://www.reddit.com/r/bootcamp/comments/1qtg5qx/windows_11_installation_direct_iso_installation/?utm_source=share&utm_medium=mweb3x&utm_name=post_embed&utm_term=1&utm_content=1" />]]></content:encoded>
          <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Reviving RDP Wrapper: A Step-by-Step Guide</title>
          <link>https://rrrainielll.com/blog/reviving-rdp-wrapper-step-by-step-guide</link>
          <description>Install RDP Wrapper, enable concurrent RDP sessions, and securely connect from anywhere with Tailscale.</description>
          <content:encoded><![CDATA[Have you ever tried **Remote Desktop**? It’s pretty great, right? Fast connection, low latency, and a full desktop experience that almost feels like you’re sitting right in front of the PC.

The catch is—it’s usually limited to **Windows Pro** and **Server** editions. If you’re on a different version of Windows, it can feel like you’re missing out.

The good news? This setup lets you **run and stream multiple RDP sessions at the same time**, making it ideal for **business use** or **personal setups with multiple users sharing one machine**. The steps are simple, straightforward, and easy to follow from start to finish and no guesswork needed.

## Prerequisites

Before we start, download the following tools:

1. **RDP Wrapper**
    
    https://github.com/stascorp/rdpwrap/releases/download/v1.6.2/RDPWrap-v1.6.2.zip
    
2. **RDPWrap Offset Finder**
    
    https://github.com/llccd/RDPWrapOffsetFinder/releases/download/v0.8/RDPWrapOffsetFinder-0.8.zip
    

---

## Step-by-Step Setup

### **1. Temporarily Turn Off Antivirus**

- **Temporarily disable your antivirus or Windows Defender**
- This tool **does NOT contain a virus**
    
    It’s often flagged because it modifies system services related to Remote Desktop, which security software sees as “suspicious behavior”
    
    !image.png
    
- Once everything is set up, you can turn your antivirus back on

> 💡 Tip: If you don’t want to fully disable your antivirus, you can simply add the RDPWrap folder to exclusions instead.
> 

### 2. Install RDP Wrapper

- Extract **RDPWrap-v1.6.2.zip**
    
    !image.png
    
- Move the extracted folder to your **C:\** drive
    
    (example: `C:\\RDPwrapper`)
    
    !image.png
    

### 3. Installation

- Onnce you extracted the files to `C:\\RDPwrapper` install the RDPWrapper by clicking the install.bat
    
    Installation.mp4
    
- Stop the Remote Desktop Service
- Open **Command Prompt as Administrator** by ctrl + r
    
    Type
    
    ```jsx
    cmd
    ```
    
    Hold the **ctrl + shift** then **enter** then type
    
    ```jsx
    cd C:\RDPwrapper
    ```
    
    After that Run:
    
    ```bash
    net stop TermService /y
    ```
    
    This will stop the RDPwrapper and the remote desktop services.
    

### 4. Run Offset Finder

- Open the **RDPWrapOffsetFinder** folder and choose the folder base on your device architecture.
- Open the CMD from the folder and Run:

```bash
RDPWrapOffsetFinder.exe "C:\Windows\System32\termsrv.dll"
```

!image.png

### 5. Update the `rdpwrap.ini`

- After the scan finishes, copy the generated offsets
- Paste them into the **rdpwrap.ini** file inside the RDPWrap directory
- Save the file

### 6. Start the Remote Desktop Service Again

```bash
net start termservice
```

---

After this, **Remote Desktop should work even on Windows Home**.

### Bonus Tip: Access Your RDP Session From Anywhere with Tailscale

Tired of dealing with port forwarding, dynamic IPs, or exposing RDP directly to the internet? You can use **Tailscale** to create a secure, encrypted mesh VPN between your devices.

#### What Tailscale Does

- Creates a **private network** between your PC and your laptop/phone
- Uses your existing logins (Google, Microsoft, GitHub, etc.) for authentication
- Works **behind NAT** and most firewalls without manual port forwarding
- Encrypts all traffic end-to-end using WireGuard

#### How to Use Tailscale with This RDP Setup

1. **Install Tailscale on both machines**
    - Download and install Tailscale on your **host PC** (where RDP Wrapper is installed)
    - Install Tailscale on your **client device** (laptop, another PC, etc.)
2. **Log in using the same Tailscale account**
    - Sign in with the same email or identity provider on all devices
    - Once logged in, both devices will appear on your Tailscale network
3. **Get the Tailscale IP of your host PC**
    - Open the Tailscale app on the **host PC**
    - Copy the **Tailscale IP address** (usually starts with `100.x.x.x`)
4. **Connect via Remote Desktop over Tailscale**
    - On your client device, open **Remote Desktop Connection**
    - Instead of using your local IP, enter the **Tailscale IP** of your host PC
    - Log in as usual with your Windows account

#### Why This Is Better Than Exposing RDP

- No need to **open ports** on your router
- Your RDP port stays **closed to the public internet**
- You still get **fast, low-latency RDP streaming** from almost anywhere with internet access

With this, your RDP setup becomes not just powerful, but also much safer to use over the internet.]]></content:encoded>
          <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
        </item>
<item>
          <title>Is Docker Dying? Not Even Close.</title>
          <link>https://rrrainielll.com/blog/is-docker-dying</link>
          <description>Docker isn't dying. Learn why containers still matter and what every developer should know about Docker today.</description>
          <content:encoded><![CDATA[# Is Docker Dying? Not Even Close.

Every few months, someone asks the same question:

> "Is Docker dying?"

The short answer is **no**.

What has changed is how developers use Docker. It is no longer the only name associated with containers, but it continues to be one of the most important tools in modern software development.

## Why People Think Docker Is Dying

### Kubernetes Took the Spotlight

When Kubernetes became the standard for container orchestration, many assumed it replaced Docker.

In reality, Kubernetes replaced **Docker Engine as its runtime**, not the Docker workflow itself. Today, Kubernetes commonly uses runtimes like **containerd** or **CRI-O**, both of which were heavily influenced by Docker's ecosystem.

### Docker Desktop Licensing

Docker introduced licensing changes for Docker Desktop, leading some companies to switch to alternatives such as Podman, Rancher Desktop, or OrbStack.

### More Alternatives Exist

Today's container ecosystem is much larger than it was a few years ago.

- Podman
- containerd
- CRI-O
- Rancher Desktop
- OrbStack
- Finch

## Docker Is Still Everywhere

Most applications are distributed as Docker images.

- PostgreSQL
- Redis
- Nginx
- Jellyfin
- Nextcloud
- Grafana
- Prometheus
- Home Assistant

## Docker Compose Remains One of the Best Developer Tools

```bash
docker compose up -d
```

```yaml
services:
  postgres:
    image: postgres:17

  redis:
    image: redis:8
```

## Should You Still Learn Docker?

Absolutely.

If you're interested in self-hosting, DevOps, backend development, cloud computing, homelabs, or Kubernetes, Docker is still one of the best places to start.

## Final Thoughts

Docker is not dying. It has simply become part of a larger container ecosystem built on open standards. Whether you use Docker, Podman, or Kubernetes, understanding containers is still an essential skill for modern developers.]]></content:encoded>
          <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
        </item>
    </channel>
  </rss>