安裝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.

MS SQL 維護計劃 備份到NAS共用資料夾

環境:

AD

NAS

MS SQL

異常狀況:

MS SQL 維護計劃 在設定DB備份的路徑，不能指定到NAS上的共用資料夾。

解決過程:

維護計劃在備份時，執行的身份通常是預設的一個系統服務帳號，可以到"服務"去查。

因為沒辦法在NAS上的共用資料夾上指派存取權限給這個帳號。

所以要換個方法

1.先在AD建立一個群組，然後把MS SQL這台主機的電腦帳號，加到這個群組。

2.接著在NAS上的共用資料夾，指派AD群組有修改權限。

這樣就完成了，備份時，這台主機就直接有權限讀寫，不會被SQL服務執行的身份給影響。

Environment:

Active Directory (AD)

NAS

Microsoft SQL Server

Issue:

When configuring a database backup destination in an MS SQL Server Maintenance Plan, the backup cannot be written directly to a shared folder on a NAS.

Resolution:

When a Maintenance Plan runs, it typically executes under the security context of a SQL Server service account (which can be identified in Services).

Since it is often not possible to assign permissions on the NAS shared folder directly to this service account, the following approach can be used:

1. Create a new Active Directory security group.
2. Add the computer account of the SQL Server to this AD group.
3. On the NAS shared folder, grant the AD group Modify permissions.

With this configuration, the SQL Server host can access the shared folder using its computer account permissions, allowing the Maintenance Plan to read from and write to the NAS share without being affected by the specific SQL Server service account being used.

Backup exec 備份MS SQL時 只能完整備份

 環境:

Backup exec 

Commvault

MS SQL

異常狀況:

Backup exec 備份MS SQL時，，設定差異備份，還是只會執行完整備份

解決過程:

Commvault 虛擬機備份設定中，如果選擇了File System and Application Consistent，就會把之前Backup exec 對MS SQL備份的備份鏈資訊重置，造成Backup exec之後備份必須做完整備份。

所以要把Commvault 虛擬機備份設定改成下面的Crash Consisten。

Environment:

Backup Exec

Commvault

Microsoft SQL Server

Issue:

When using Backup Exec to back up MS SQL Server, the job is configured for Differential Backup, but it always performs a Full Backup instead.

Resolution:

In the Commvault virtual machine backup settings, if “File System and Application Consistent” is enabled, it resets the SQL backup chain information previously created by Backup Exec.

As a result, Backup Exec is forced to perform a new Full Backup before Differential Backups can continue.

To avoid this issue, change the Commvault VM backup setting from:

• File System and Application Consistent

to:

• Crash Consistent

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

環境:

m365 office

異常狀況:

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

解決過程:

比對後發現，因為m365 office會自動更新，有些更新到最新的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)

HUKE HK100藍牙折疊鍵盤

在淘寶找了一個折疊鍵盤搭配平板使用。

HUKE HK100，折起來大概比手掌還大一點點，轉軸的地方還行，但沒到很扎實。

用起來都蠻順的，旁邊數字鍵功能都沒啟用，就當滑鼠用而已。

缺點大概就是按鍵上沒有注音符號。

出門帶平板加折疊鍵盤，比帶一台筆電還方便。

 

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.

國際牌冷氣 無線控制模組 CZ-T007 設定

1.  CZ-T007 先安裝到冷氣機上，安裝時，冷氣機無需斷電。

2.  搖控器拔掉電池，然後按住"溫度上跟下鍵"，裝上電池，看到搖控器顯示 "31 bu"的畫面時，放掉上下鍵。

3. 按下"下鍵"，畫面會顯示 "31SA"

4. 開啟手機中安裝的Panasonic IOT app。

5. 選擇"新增裝置"，選擇無線模組。

6. 照app上的操作，先開啟手機的wifi功能，連上這個無線模組的WIFI，然後再輸入家中的wifi帳號/密碼。

7. 這樣就新增成功了，但要記住，搖控器不能改回原本的樣子了，就保持在"31SA"這個模式下，這時搖控器畫面雖然不會顯示其他的東西，但開關機的功能還是可以用，其他的就在手機上操作。

如果搖控器改回原本的操作模組，無線模組就會無法使用。

 環境:

commvault

掛載nas共用資料夾，當作媒體櫃，存放備份資料。

異常狀況:

nas密碼變更後，commvault無法掛載共用資料夾

解決過程:

在控制台，裡面有credentials manager，裡面有目前使用的帳號密碼設定，可以從這邊去修改。

ESXI 變更密碼 失敗 - 發生一般系統錯誤: Weak password: is based on the old one. *** passwd: Authentication token manipulation error

 環境:

esxi

異常狀況:

無法變更，會出現錯誤

解決過程:

在系統裡的進階設定，裡面有一個Security.PasswordQualityControl 參數。

在裡面加入 similar-permit ，存檔後馬上生效，就可以變更密碼了。

使用LDAP與AD連線出現異常

 環境:

win2025 AD

異常狀況:

PHP程式要用LDAP協定，透過domain name抓ad使用者資料，時好時壞，改用IP連線也是。

連到不用的DC主機都會有狀況。

解決過程:

DC主機上的本機安全性原則中，在"電腦設定->windows設定->安全性設定->網域控制站:LDAP伺服器簽署要求強制執行"，要設定成停用，每台DC都要設定成停用，就可以排除問題。

Environment:

Windows Server 2025 Active Directory

Issue:

A PHP application uses the LDAP protocol to query AD user information via the domain name, but the connection is unstable (intermittently works and fails).
Using the DC’s IP address shows the same issue.

The problem occurs when connecting to certain domain controllers.

Resolution:

On the domain controllers, modify the Local Security Policy:

• Go to:
  Computer Configuration → Windows Settings → Security Settings → Domain Controller: LDAP server signing requirements
• Set it to Disabled

This setting must be applied to all domain controllers.

After applying the change, the issue is resolved.

Commvault 備份虛擬機 突然變的很慢

環境:

Commvault 備份虛擬機

異常狀況:

對新的虛擬機做第一次備份，可能容量比較大，過程中又有其他的備份，造成效能問題，最後就停住多個小時後，手動取消。

但後來要重新備份時，傳輸速度變超級慢，速度大概只剩之前的1/7~8，重開機也一樣。

解決過程:

後來發現之前備份失敗後，虛擬機上有一份snapshot沒被移除，先在esxi上，把那份snapshot刪除後，重新備份，就正常了。

Environment:

Commvault (VM Backup)

Issue:

When performing the first backup of a new virtual machine, the data size was relatively large. During the process, other backup jobs were also running, causing performance issues. Eventually, the job became unresponsive and was manually canceled after several hours.

After that, when attempting to run the backup again, the transfer speed became extremely slow, dropping to about 1/7–1/8 of the original speed. Restarting the system did not resolve the issue.

Resolution:

It was later discovered that after the failed backup, a snapshot remained on the virtual machine and was not removed.

By logging into ESXi and deleting the leftover snapshot, then running the backup again, the performance returned to normal.

ESXI 無法開啟虛擬機器 xxx的電源。開啟模組 monitorloop 的電源失敗

  環境:

ESXI  

Synology active backup business

異常狀況:

用Synology active backup business備份的虛擬機，還原到其他esxi後，開機出現錯誤。

解決過程:

原機配置了較高的CPU與RAM，還原後，目的esxi上資源不足，無法開機，把虛擬機的CPU與RAM調低後，就可以正常開機

Environment:

ESXi
Synology Active Backup for Business

Issue:

After restoring a virtual machine using Synology Active Backup for Business to another ESXi host, the VM fails to power on and shows an error.

Resolution:

The original VM was configured with relatively high CPU and RAM.
After restoration, the target ESXi host did not have sufficient resources to support that configuration.

By reducing the VM’s CPU and RAM allocation, the virtual machine was able to power on normally.

ESXI VMFS 增加容量失敗-無法變更主機組態。

 環境:

ESXI 6.7

異常狀況:

底層硬碟RAID擴充完一顆新硬碟後，要在ESXI上也對儲存區進行擴充。

在web console上操作，對著要擴充的datastore ，選擇"增加容量"。

再來選擇"擴充現有..........."。

第三步，要先在分割之前的圖，點選vmfs區塊，然後就會出現一個調整新增容量的設定，選擇要把新增的硬碟，擴充多少容量到vmfs中。

按下完成後，就會出現錯誤，試了很多次，擴充不同的容量，都一樣錯誤:

說明:延伸 VMFS 資料存放區範圍的容量

狀態:失敗 - 無法變更主機組態。

解決過程:

用指令的方式擴充，就成功了。

Environment:

ESXi 6.7

Issue:

After expanding the underlying RAID by adding a new disk, the datastore also needs to be extended in ESXi.

When performing the operation via the web console:

1. Select the datastore and choose “Increase capacity”
2. Then select “Expand existing…”
3. In the partition layout screen, select the VMFS partition, and adjust how much of the newly added space should be allocated to VMFS

However, after clicking Finish, the following error occurs regardless of the size selected:

• Description: Extend VMFS datastore capacity
• Status: Failed – Unable to change the host configuration

Resolution:

Expanding the datastore using the command line (CLI) was successful.

DHCP 設定匯出匯入

DHCP config export command

netsh dhcp server export d:\backup.txt all

DHCP config import command

 netsh dhcp server import d:\backup.txt all

SQL management tool連線時出現錯誤:此憑證鏈結是由不受信任的授權單位發出的

 

環境:

MS SQL2022

異常狀況:

SQL management tool連線時出現錯誤:此憑證鏈結是由不受信任的授權單位發出的

解決過程:

錯誤訊息「此憑證鏈結是由不受信任的授權單位發出的」是因為 SQL Server 2022 預設強制執行加密連線。

勾選下面的「信任伺服器憑證」選項，即可正常登入。

Environment:

MS SQL Server 2022

Issue:

When connecting using the SQL management tool, the following error appears:

“The certificate chain was issued by an authority that is not trusted.”

Resolution:

This error occurs because SQL Server 2022 enforces encrypted connections by default.

Enable the “Trust Server Certificate” option in the connection settings, and then you will be able to log in normally.

SQL 2022安裝時卡住不動

環境:

MS SQL2022

Kaspersky endpoint security

異常狀況:

MS SQL2022安裝到一半停住很久，cpu跟ram的使用資源都不會動。

解決過程:

將Kaspersky endpoint security防護暫停後，就會繼續安裝過程，完成剛裝

Environment:

MS SQL Server 2022
Kaspersky Endpoint Security

Issue:

During the installation of MS SQL Server 2022, the setup process gets stuck for a long time.
CPU and RAM usage remain unchanged and the installation does not continue.

Resolution:

After temporarily disabling Kaspersky Endpoint Security protection, the installation process resumes and completes successfully.

Synology 取消 "此裝置以後不需要驗證"

 環境:

Synology  NAS啟用 2FA的"此裝置以後不需要驗證"，需要取消

解決過程:

管理者登入後，到使用者設定中，在該帳號底下，選擇"登出所有裝置"，就會跳出說明，提醒這樣也會取消信任裝置。

之後同設備要登入時，就要輸入2FA的驗證碼。

Environment:

On a Synology NAS, 2FA is enabled and the option “Trust this device / Do not require verification on this device in the future” needs to be revoked.

Resolution / Steps:

1. Log in as an administrator.

2. Go to User settings.

3. Under the target user account, select “Sign out of all devices”.

4. A prompt will appear explaining that this action will also revoke trusted devices.

After this, when the same device logs in again, it will be required to enter the 2FA verification code.