diff --git a/blog/posts/01-22-2025 - Windows Power Profiles and Potential Performance Losses.md b/blog/posts/01-22-2025 - Windows Power Profiles and Potential Performance Losses.md
new file mode 100644
index 0000000..3f99d6a
--- /dev/null
+++ b/blog/posts/01-22-2025 - Windows Power Profiles and Potential Performance Losses.md	
@@ -0,0 +1,19 @@
+---
+draft: false 
+date: 2025-01-22
+updated: 2025-01-22
+authors:
+  - nicole
+categories:
+  - General
+tags:
+  - Windows Server
+  - Power Profiles
+  - Virtualization
+---
+
+# Windows Power Profiles and Potential Performance Losses
+So I've been noticing a trend recently regarding something I never really took much time to consider, but later realized had huge potential to impact performance of potentially both physical and virtual servers.  (I have not personally seen it affect virtual machines, but it's plausible it could happen).
+
+## Overview of the Problem
+The general idea is that Windows devices (Workstations & Servers) both have power "**profiles**".  These profiles, by default, are set to "Balanced".  Which in basic terms means that the operating system will artificially limit the CPU speed to below 2.0GHz.  
\ No newline at end of file
diff --git a/blog/posts/12-18-2024 - Placeholder.md b/blog/posts/12-18-2024 - Placeholder.md
deleted file mode 100644
index 684f24e..0000000
--- a/blog/posts/12-18-2024 - Placeholder.md	
+++ /dev/null
@@ -1,17 +0,0 @@
----
-draft: false 
-date: 2024-12-27
-updated: 2024-12-27
-authors:
-  - nicole
-categories:
-  - General
-  - Documentation
-tags:
-  - MKDocs
-  - Material MkDocs
-  - Documentation
----
-
-# Placeholder
-Placeholder Blog Post
\ No newline at end of file