windbg 查看 memory dmp檔

環境:

win11

windbg

異常狀況:

用windbg 開啟dmp檔，看不到裡面的log分析。

解決過程:

點選 command browser。

執行 !analyze -v ，就會出現記錄，可以查看是什麼原因造成系統異常。

solidworks 按 del 鍵沒反應

環境:

solidworks

異常狀況:

del 鍵失效，在圖中對任何東西按下del鍵，都無法刪除，沒任何反應

解決過程:

solidworks內對刪除的快速鍵設定不見造成此問題。

從"工具" ->"自定"->"鍵盤"，裡面會有"刪除"的快速鍵可以設定，這邊選擇del鍵，就可以恢復del鍵的刪除功能。

Environment:

SolidWorks

Issue:

The Delete (Del) key stops working.
Pressing the Del key on any object within a drawing or model has no effect, and nothing is deleted.

Resolution:

The issue is caused by the Delete keyboard shortcut assignment being removed or changed within SolidWorks.

To restore the Delete key function:

1. Go to Tools → Customize.
2. Select the Keyboard tab.
3. Locate the command Delete.
4. Assign the Del key as its keyboard shortcut.
5. Apply the changes.

After reassigning the shortcut, the Del key will function normally and can be used to delete objects again.

commvault Alert: Index State Type: Custom Rules - Index State

   環境:

commvault

異常狀況:

突然每天都會收到這個警告信，但備份工作都正常，不知是哪邊有問題。

後來發現這個backupset底下的所有虛擬機備份，在這警告信出現前的備份都可以正常還原。

在開始發出警告信後的備份，還原時都會出現錯誤:Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details。

解決過程:

參考ai上的作法，在commvault主機上的C:\Program Files\Commvault\ContentStore\IndexCache，底下有CvIdxDB跟CvIdxLogs資料夾

在裡面找到跟上面DbName相同名稱的資料夾，把他們改名。

重新建立還原工作，系統就會重建裡面的內容，恢復正常~~但試過沒用。

後來重新啟動完整備份，還是一樣的錯誤。

最後解法就是，建一個新的backupset，在裡面對虛擬機建立新的備份工作，備份完測試，可正常還原。

Environment:

Commvault

Issue:

An alert email suddenly started appearing every day, although all backup jobs were completing successfully and no obvious issues were found.

Further investigation showed that:

• Backups of all virtual machines under this Backupset that were created before the alert emails started could be restored normally.

• Backups created after the alerts began failed during restore with the following error:

Error:
Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details.

Troubleshooting Process:

Based on suggestions found online, the following method was attempted:

1. On the Commvault server, navigate to:
   C:\Program Files\Commvault\ContentStore\IndexCache

2. Locate the folders under CvIdxDB and CvIdxLogs that have the same name as the DbName shown in the error.

3. Rename those folders.

4. Create a new restore job so the system can rebuild the index data.

However, this method did not resolve the issue.

A Full Backup was then executed again, but the restore error still occurred.

Final Resolution:

The issue was resolved by:

1. Creating a new Backupset.

2. Creating a new backup job for the virtual machines within that Backupset.

3. Running the backup again.

After the new backup completed, restore tests were performed and the restore worked normally.

安裝win11 抓不到pcie ssd硬碟。

 環境:

acer主機

Intel 13代 cpu

pcie ssd

異常狀況:

安裝win11，一直抓不到ssd硬碟。

上acer官網找到了irst的驅動，安裝時這個驅動也不支援，還是找不到硬碟。

上intel官網抓到最新一代的irst驅動，卻是exe檔，在win11安裝過程，也沒辦法安裝

解決過程:

intel官網抓到最新一代的irst驅動是exe檔，需在其他台電腦，用powershell指令，去解壓縮，裡面就會有driver這個資料夾。

安裝win11時就可以透過裡面的檔案，載入pcie ssd。

1. 在包含SetupRST.exe檔的目錄中打開終端，方法是右鍵按兩下目錄並在此處選擇「在終端中打開」或「打開 PowerShell」。您可能必須在目錄上按 SHIFT 鍵，才能看到要選擇的正確選項。
2. 透過執行命令 ./SetupRST.exe -extractdrivers SetupRST_extracted 來解壓縮預安裝驅動程式

Environment:

Acer desktop/laptop
Intel 13th Gen CPU
PCIe SSD

Issue:

During Windows 11 installation, the SSD drive is not detected.

The Intel Rapid Storage Technology (IRST) driver downloaded from the Acer support website was loaded during setup, but the SSD still could not be detected.

A newer IRST driver was found on Intel's website, but it was provided as an .exe installer, which cannot be installed directly during the Windows 11 installation process.

Resolution:

The latest Intel IRST package downloaded from Intel's website must first be extracted on another computer.

1. Download the latest SetupRST.exe from Intel.
2. Open a terminal (PowerShell or Command Prompt) in the folder containing SetupRST.exe.
3. Run the following command:

.\SetupRST.exe -extractdrivers SetupRST_extracted

This will extract the pre-installation drivers into a folder named SetupRST_extracted.

To open a terminal in the correct folder:

• Right-click within the folder and select "Open in Terminal" or "Open PowerShell window here".
• On some Windows versions, you may need to hold the SHIFT key while right-clicking to see the appropriate option.

4. Copy the extracted driver files to the Windows 11 installation USB drive.
5. During Windows 11 setup, select Load Driver when choosing the installation disk.
6. Browse to the extracted driver folder and load the IRST driver.

After loading the extracted driver, the PCIe SSD will be detected and Windows 11 installation can proceed normally.

M365 Outlook 寄信時 簽名檔 內的圖檔變成附件

環境:

m365 office

異常狀況:

突然有愈來愈多使用者寄出的信件，在收件人的outlook， 簽名檔 內的圖檔會破圖，如下圖，裡面會寫"無法顯示連結的影像。檔案可能已移動............."，然後那個圖會變成附件

解決過程:

比對後發現，因為m365 office會自動更新，有些更新到最新的outlook，才會有這種問題。

然後在去檢查，才發現是圖片如果有設定成"文繞圖"，這個圖變成附件。

只要把"文繞圖"改成"與文字排列"就沒問題了。

後來m365 office自己也把那個問題處理掉了。

版本 2605 (建置 20026.20140)

解決的問題

Word

• 修正了在經典 Outlook 中使用 上下 文字換行時圖片無法顯示的問題。

Environment:

Microsoft 365 Office / Outlook

Issue:

An increasing number of users suddenly found that images in their email signatures were broken when viewed by recipients in Outlook.

The image area displayed the message:

“The linked image cannot be displayed. The file may have been moved…”

The image would also appear as an attachment in the email.

Resolution:

After comparison and testing, it was found that the issue only occurred on systems updated to the newer versions of Outlook through Microsoft 365 automatic updates.

Further investigation showed that the problem occurs when the signature image is configured with a text wrapping option.

If the image wrapping style is changed from “Wrap Text” to “In Line with Text”, the issue is resolved and the image displays normally in the email signature.

Backup exec 2014 無法正常啟動

 環境:

windows 2012

backup exec 2014

異常狀況:

windows 2012 做完windows update，安裝完backup exec 2014，執行都會出現錯誤訊息，無法使用

Backup exec 啟動時跳出錯誤，必須直接關閉

問題事件名稱: CLR20r3 

問題簽章 01: BackupExec.exe 

問題簽章 02: 14.1.1786.0 

問題簽章 03: 5371d883 

問題簽章 04: mscorlib 

問題簽章 05: 4.8.4110.0 

問題簽章 06: 5de6dafa 

問題簽章 07: 113a

解決過程:

因為windows 系統在做更新時，裝了frameworks4.8，需要把它移除後，backup exec才能運作。

可參考官網說明

 https://www.veritas.com/support/en_US/article.100055701

卸载 .NET Framework 4.8 并重新启动服务器。此更新将在已安装的更新列表中显示为 KB4486105 （Windows 2012 R2）、KB4486081 （Windows 2012）、KB4486129 （Windows 2016）、KB4486153 （Windows 2019）。

Environment:

Windows Server 2012
Backup Exec 2014

Issue:

After installing Windows Updates on Windows Server 2012 and then installing Backup Exec 2014, Backup Exec fails to start and immediately crashes with an error message.

Error details:

• Problem Event Name: CLR20r3
• Application Name: BackupExec.exe
• Application Version: 14.1.1786.0
• Fault Module Name: mscorlib
• Fault Module Version: 4.8.4110.0

Backup Exec displays an error on startup and must be closed immediately.

Resolution:

The issue is caused by Windows Update installing .NET Framework 4.8, which is incompatible with Backup Exec 2014.

Removing .NET Framework 4.8 and rebooting the server allows Backup Exec to function normally again.

Reference:
https://www.veritas.com/support/en_US/article.100055701?utm_source=chatgpt.com

The .NET Framework 4.8 update may appear in Installed Updates as:

• KB4486105 (Windows 2012 R2)
• KB4486081 (Windows 2012)
• KB4486129 (Windows 2016)
• KB4486153 (Windows 2019)

COMMCAULT DR備份 Error Code [34:53] [34:53]

環境:

COMMCAULT

異常狀況:

存放DR備份的網路資料夾密碼有變更，之後DR備份就會有錯誤訊息

Error Code [34:53] [34:53] 

Failure Reason CommServeDR: Destination Directory [\\sharefolder\commvault\CVDRBackup] does not exist or is inaccessible 

CommServeDR: Destination Directory [\\sharefolder\commvault\CVDRBackup] does not exist or is inaccessible 

解決過程:

到commvault console裡的"控制台"，找到"DR Backup"，裡面可以變更網路資料夾的帳號與密碼，修改正確後就可以正常備份。

環境:

WIN11 25h2

Logitech meet up視訊設備

異常狀況:

使用Teams，或其他網頁，搭配內建的喇叭/麥克風，功能正常。

但Logitech meet up的喇叭/麥克風，就會失效，Teams還會跳出錯誤提示。

解決過程:

查看event log，會看到錯誤訊息

失敗的應用程式名稱： AUDIODG.EXE，

版本： 10.0.26100.8246，

時間戳記： 0x923cfbc9 

錯誤模組名稱： igo_src.dll，

 版本： 3.0.0.0，時間戳記： 0x642f89de 

例外狀況代碼： 0xc0000005 

錯誤位移： 0x000000000001d019 

錯誤處理常式識別碼： 0x788 

失敗的應用程式開始時間： 0x1DCD6189BA1A78A 

Faulting 應用程式路徑： C:\WINDOWS\system32\AUDIODG.EXE Faulting 

模組路徑： C:\WINDOWS\System32\DriverStore\FileRepository\igoapo.inf_amd64_50fe8789ddef31f8\igo_src.dll

這個錯誤關鍵是明顯音效處理模組故障，不是羅技設備本身壞掉。

最快的方式就是把內建的喇叭/麥克風的驅動程式移除，改裝舊一點的驅動，就正常了。

Environment:

Windows 11 25H2

Logitech Meetup video conferencing device

Issue:

When using Teams or web applications with the built-in speaker/microphone, everything works normally.

However, when switching to the Logitech Meetup speaker/microphone, the audio devices fail, and Teams shows an error message.

Investigation:

In Event Viewer, the following error can be found:

Faulting Application Name: AUDIODG.EXE

Faulting Module Name: igo_src.dll

Exception Code: 0xc0000005

Module Path: C:\Windows\System32\DriverStore\FileRepository\igoapo.inf...\igo_src.dll

This indicates a failure in the audio processing module (APO) rather than a hardware issue with the Logitech device itself.

Resolution:

The root cause is related to the built-in audio driver.

By:

Uninstalling the current built-in speaker/microphone driver

Installing an older (stable) version of the audio driver

The issue is resolved, and the Logitech Meetup device functions normally again.

M365 office 的出現錯誤 : Symmetric Key Derivation Function version 'KDFV1' is invalid

環境:

M365 office

異常狀況:

OUTLOOK開啟會出現下列錯誤，

解決過程:

進到windows的"設定"->"帳戶"->"存取公司或學校資源"。

把裡面不需要的帳戶全部中斷連線，重新開啟outlook，就可以正常登入使用了。

Environment:

Microsoft 365 Office / Outlook

Issue:

When opening Outlook, an error message appears and Outlook cannot be used normally.

Resolution:

1. Open Windows Settings
2. Go to Accounts → Access work or school
3. Disconnect all unnecessary accounts listed there
4. Reopen Outlook

After removing the unused accounts, Outlook should log in and function normally again.

commvault 備份時會當機

  環境:

commvault

x3650m3

win2012

異常狀況:

已經運作多年的備份主機，突然開始在備份時會當機，備份比較大的資料才會當機，只是少量的就不會，不執行備份放一整個晚上也都沒問題。

當機後通常會進到藍底白字畫面，搜尋相關錯誤資訊，但未有任何進度就會直接重開機。

沒有memory dump檔，事件檢視器也沒有任何可參考的資訊，只會有意外當機的事項。

IMM 的log裡也沒有任何的異常。

raid程式裡，硬碟與raid卡都健康。

用內建的記憶體測試，正常。

解決過程:

關閉防毒->無效

調低備份的Maximum number of parallel data transfer operations->無效

關機拔電後重開->無效

拔掉六條記憶體擦一擦，只插回基本的兩條->無效

在找不到任何方法下，先把記憶體全部插回，再試試，居然就正常了....

但過了一週，又開始發生備份會當機的狀況，大概兩天後主機的raid跟pci就亮橘燈了。

更換raid卡後終於恢復正常。

Environment:

Commvault
IBM x3650 M3
Windows Server 2012

Issue:

A backup server that had been running normally for many years suddenly began crashing during backup operations.
The crash only occurred when backing up large amounts of data. Backups with small amounts of data completed normally, and the server could remain powered on overnight without issues if no backup jobs were running.

After the crash, the system usually entered a blue screen. When attempting to view the error details, the system rebooted before any useful information could be collected.

Additional observations:

• No memory dump files were generated.

• Event Viewer only recorded an unexpected shutdown with no useful details.

• IMM logs showed no abnormalities.

• RAID management reported that the disks and RAID controller were healthy.

• The built-in memory diagnostic test passed without errors.

Troubleshooting Process:

• Disabled antivirus → No effect

• Reduced Maximum number of parallel data transfer operations in Commvault → No effect

• Powered off the server and unplugged power before restarting → No effect

• Removed six memory modules, cleaned them, and left only two installed → No effect

With no other solutions available, all memory modules were reinstalled again.
Unexpectedly, after reinstalling all the RAM, the system returned to normal operation and the backup jobs completed successfully.

However, about one week later, the backup server began to crash again during backup jobs.

After approximately two more days, the RAID and PCI indicator lights on the server turned orange.

The RAID controller was then replaced, and after replacing the RAID card, the system finally returned to stable operation and the backup crashes stopped.

Windows 資料夾透過FASTCOPY同步到NAS共用資料夾 權限並沒有同步

 環境:

Windows 資料夾透過FASTCOPY，同步到NAS共用資料夾

異常狀況:

資料夾開始建立進行同步時，發現權限並沒有同步過去

解決過程:

研究了很久，發現測試的資料夾正常，正式要同步的資料夾會有問題。

原來是資料夾第一次在同步時，還沒全部完成前去查看資料夾權限時，不會是最後的結果，所以要等同步完再檢查，就會發現資料夾的ACL權限有全部同步過去了。

Environment:

Windows folders synchronized to a NAS shared folder using FastCopy.

Issue:

When the folder creation and synchronization start, the folder permissions (ACLs) do not appear to be synchronized to the NAS.

Resolution / Findings:

After extensive investigation, it was found that test folders behaved normally, while the production folders showed this issue.

The root cause is that during the initial synchronization, if you check the folder permissions before the sync process has fully completed, the permissions shown are not the final result.
Once the synchronization finishes completely and you recheck the folder permissions, you will see that the ACL permissions have been fully and correctly synchronized.

筆電安裝win10/11 找不到ssd硬碟

環境:

ASUS or ACER筆電

異常狀況:

重灌win10 or win11系統時，在選擇要安裝在哪個磁區，不會顯示ssd硬碟的磁區。

解決過程:

1.下載irst這個驅動程式，asus網站上有提供。

https://www.asus.com/tw/supportonly/irst/helpdesk_download/

2.將該程式放入win10 or win11的安裝usb中。

3.安裝win10 or win11系統時，在選擇要安裝在哪個磁區的步驟，選擇載入驅動程式，然後選擇irst。

4.ssd磁碟就會正常顯示出來。

Environment:

ASUS or ACER laptops

Issue:

When reinstalling Windows 10 or Windows 11, the SSD drive does not appear during the disk selection step of the installation process.

Resolution / Troubleshooting Steps:

1. Download the IRST (Intel Rapid Storage Technology) driver (available on the ASUS website).

2. Copy the driver to the Windows 10 or Windows 11 installation USB drive.

3. During the Windows installation, at the step where you choose the disk to install the OS, select Load driver, then choose the IRST driver.

4. The SSD drive will then be displayed correctly.

點選右下角的日期時間 不會跳出月曆

   環境:

WIN 11點選右下角的日期時間，不會跳出月曆

解決過程:

1.windows鍵+ r鍵 ，輸入 regedit

2.找到HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer\

3.把DisableNotificationCenter設成 0

Environment:

On Windows 11, clicking the date and time in the bottom-right corner does not display the calendar.

Resolution :

1.Press Windows key + R, then type regedit.

2.Navigate to:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer\

3.Set DisableNotificationCenter to 0.

Blogger裡面的廣告突然都沒了

    環境:

Google blogger + adsense

異常狀況:

多年前我的 blogger有申請adsense，想賺點廣告費，一開始的確也有看到有廣告收到，但大概在兩三年前，發現收入一直沒增加，點開網站才發現通通都沒廣告了。

但在adsense上的設定都沒去調整，狀態都是正常的，也設定了自動廣告，版面上也有設定廣告的視窗。

但就是沒廣告。

解決過程:

 之前上網查都沒什麼有用的解決。

後來gemini出現了，就想說問它看看，結果gemini說要在主題裡，用html編輯，插入一段語法，結果插入存檔後。

直接重新開啟網頁，裡面廣告馬上就出現了，太神奇了。

gemini的說明如下:

檢查自動化廣告的程式碼（重要！）

• 在 Blogger 後台，進入 「主題」(Theme) 或 「範本」 設定。

• 點擊 「編輯 HTML」(Edit HTML)。

• 請檢查在 HTML 程式碼中，<head> 標籤之後，是否存在以下格式的 AdSense 程式碼片段：

  HTML

  <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-您的發布商 ID" crossorigin="anonymous"></script>
  

  （ca-pub-您的發布商 ID 應替換為您自己的 ID）

• 如果找不到這段程式碼， 這就是問題所在。您需要從 AdSense 後台重新取得**「自動化廣告」**的程式碼，並將其貼到 Blogger 的 <head> 區塊內。

Environment:

Google Blogger + AdSense

---

Issue:

Many years ago, I applied for AdSense on my Blogger site to earn some ad revenue. At first, I did see ads and some earnings coming in. However, around two or three years ago, I noticed that my revenue had stopped increasing. When I opened the site, I realized that all the ads had disappeared.

I hadn’t changed any settings in AdSense; everything still showed as normal. Auto ads were enabled, and ad slots were configured on the layout.

But no ads were showing.

---

Troubleshooting Process:

I previously searched online but couldn’t find any helpful solutions.

Later, when Gemini came out, I decided to ask it. Gemini suggested editing the theme’s HTML and inserting a specific code snippet. After inserting the code and saving the changes…

I refreshed the site, and the ads appeared immediately. It was amazing.

In the Blogger dashboard, go to “Theme” and click “Edit HTML.”

Check whether the following AdSense code snippet exists right after the <head> tag:

<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-YourPublisherID" crossorigin="anonymous"></script>

(ca-pub-YourPublisherID should be replaced with your own publisher ID.)

If this code is missing, this is the root cause.
You need to go to the AdSense dashboard, retrieve the Auto Ads code again, and paste it into the <head> section of your Blogger theme.

solidworks功能表中文亂碼 中文名稱的STEP檔無法開啟

 win11安裝solidworks 後，出現一些功能表中文是亂碼、有中文名稱的STEP檔無法開啟

要進到"選用功能"，把"台灣地區"這個選項解除安裝。

重灌電腦 出現 "選取的磁片具有mbr磁碟分區表格....." 錯誤，沒有顯示電腦內的硬碟

  環境:

DEll筆電，要重灌WIN11

異常狀況:

用WIN11 USB重灌電腦時， 出現 "選取的磁片具有mbr磁碟分區表格....." 錯誤，裡面只有顯示USB磁碟，但電腦內的硬碟卻沒抓到。

解決過程:

進入到bios設定中，去storage裡面，原本是選擇raid on，改成ahci/nvme，在重開機，就可以正常重灌系統了。

Environment 

Device: Dell laptop

Goal: Reinstalling Windows 11

Problem/Error Description 

When attempting to reinstall Windows 11 using a Windows 11 USB installation drive, the following error message appeared: "The selected disk has an MBR partition table..."

The system only displayed the USB drive as an available disk, but the internal hard drive (or SSD) was not detected by the installation program.

Solution 

Enter the BIOS/UEFI Setup menu.

Navigate to the Storage or SATA Operation settings.

The original setting was RAID On (or Intel VMD/RST).

Change the setting from RAID On to AHCI/NVMe.

Save the changes and restart the computer.

The system installation (reinstallation) can now proceed normally, as the internal drive is detected.

ASUS ESC700 G3 開機一直進BIOS

  環境:

ASUS ESC700 G3

WIN7

異常狀況:

當機之後，開機就會一直直接進到BIOS，從BIOS裡的資訊看的出來有抓到硬碟。

但把線重新拔插，重開機後，還是一樣狀況

解決過程:

把該硬碟接到別台主機，可正常開機。

拿其他台電腦的硬碟來接上有問題的主機，也可正常開機。

所以判斷硬碟跟主機板都沒問題，應該就是BIOS設定問題。

BIOS設定裡面的"啟動"->"作業系統類型"，本來是選擇"windows uefi模式"，將它改成"其他作業系統"，然後重開機後就正常了。

WIN2025DC 開啟其他DC的共用資料夾存取被拒 KDC不支援所要求的加密類型

  環境:

DC主機作業系統: win2022 & win2025

網域&樹系功能等級: 2016

異常狀況:

win2025dc剛登入系統後，連線任何dc的共用資料夾都是正常的，但大概半小時後，就無法連線，會跳出存取被拒的視窗，要求重新輸入帳號密碼。而且畫面右下角還會跳出"windows需要您目前的認證"

所有的win2025dc都有這個問題，但win2022dc都沒這個問題。

後來有做一個測試:

1.在dc上執行klist purge，清除所有票證

2.接著執行klist get krbtgt。

沒問題的dc就可以抓到票證，但有問題的dc就會出現KDC不支援所要求的加密類型。

經調查，是administrator密碼很久沒變更，使用的是rc4的加密協定，但win2025dc預設會不支援。

所以就是把domain administrator帳號裡，勾選支援aes 128跟256位元加密類型，然後再重設administrator的密碼，就可以排除這個問題。

DC作業系統 網域功能等級 樹系功能等級 升級-win2025 dc無法登入

 環境:

DC主機作業系統: win2012r2

網域&樹系功能等級: 2003

升級流程:

1. 新增win2022 DC主機，設定5大角色

2. 移除win2012r2 DC主機

3. 網域&樹系功能等級升級到2016

4. 新增win2025 DC主機，出現異常

異常狀況:

不管新增幾台win2025 DC主機，升級成DC角色重開機後，win2025 DC主機遠端桌面或本機無法登入，都會出現帳號密碼有錯，安裝最新的windows更新，使用不同的domain admin帳號登入都一樣無法登入

解決過程:

上網查詢相關解法，可以先在win2022DC主機上，用ps session連到win2025DC主機，把KDC服務關閉，就可以登入win2025DC，但登入後，就算把KDC服務開啟，也是無法正常與其他DC主機同步。

試過ChatGPT提供的很多方法，都無法解決，但在一些文件上有看到重設krbtgt這個系統帳號的密碼，就可以解決問題了，很多人建議去下載一個重設krbtgt密碼的powershell，做重設密碼。

先請微軟連線確認問題，收集完相關log，也是判斷KDC服務的一些加密協定不支援，造成登入失敗，DC同步失敗等問題，因此建議重設krbtgt這個系統帳號的密碼，用ADUC去重設，沒有提供powershell來做重設。

在第一次重設krbtgt密碼後，新建的win2025主機升成DC後，就可正常登入運作了，不用等第二次重設。

但微軟有建議，要在10小時後重設第二次，所有隔天有再重設一次。

Environment

• Existing DC Operating System: Windows Server 2012 R2

• Domain & Forest Functional Level: Windows Server 2003

---

Upgrade Procedure

1. Added a new Windows Server 2022 domain controller and transferred all five FSMO roles to it.

2. Removed the Windows Server 2012 R2 domain controller.

3. Upgraded the domain and forest functional levels to Windows Server 2016.

4. Added a new Windows Server 2025 domain controller — issue occurred.

---

Issue Description

After promoting any Windows Server 2025 machine to a domain controller and rebooting, it becomes impossible to log in either locally or via Remote Desktop.
The system reports that the username or password is incorrect.
Installing the latest Windows updates or using different domain administrator accounts does not resolve the problem — all attempts to log in fail.

---

Troubleshooting Process

Based on online findings, a temporary workaround was discovered:
From the Windows Server 2022 DC, use PowerShell remoting (PSSession) to connect to the affected Windows Server 2025 DC and stop the KDC service.
After stopping the KDC service, login becomes possible.
However, once logged in, re-enabling the KDC service does not restore normal replication or synchronization with other domain controllers.

Multiple potential solutions provided by ChatGPT and other sources were tested but did not resolve the issue.
Several documents mentioned that resetting the “krbtgt” system account password could resolve similar problems. Many users recommended using a PowerShell script to perform the reset.

Microsoft was then engaged for remote troubleshooting. After reviewing the collected logs, Microsoft determined that the issue was caused by unsupported encryption protocols within the KDC service, which led to authentication and replication failures.
Microsoft advised resetting the krbtgt account password using Active Directory Users and Computers (ADUC), rather than via PowerShell.

After performing the first krbtgt password reset, newly promoted Windows Server 2025 DCs were able to log in and operate normally.
A second reset was not immediately required for functionality.

However, Microsoft still recommended performing a second krbtgt password reset after 10 hours, which was carried out the following day as advised.

redhat 備份虛擬機還原開機後出現錯誤 fsck.ext3: memory allocation failed while retrying to read bitmaps for /p1

 一台redhat 備份虛擬機，在還原到其他硬體，開機後出現錯誤

fsck.ext3: memory allocation failed while retrying to read bitmaps for /p1 

an error occurred during the file system check dropping you to a shell the system will reboot when you leave the shell

這時就先去查/p1是掛在哪個硬碟後，用root密碼登入，執行下列指令

fsck -y /dev/sda1

完成後在執行 reboot，就可以正常進入到系統了。