Win10, DISM

http://wp.me/ph3BR-25N

 

點擊 <開始> 輸入 <cmd>, 當搜索框中出現 cmd 後右鍵點擊並選擇 <Run as Administrator>

dism /online /Get-CurrentEdition

/online, 是對當前版本執行操作的關鍵參數
/Get-CurrentEdition, 查看當前版本的資訊

dism /online /Get-TargetEditions

/Get-TargetEditions, 查看當前版本可以升級到哪些其他版本

dism /online /Get-Features|more

REF:
http://ezone2.ulifestyle.com.hk/discuz/viewthread.php?tid=5612
https://wechat.kanfb.com/archives/216962

https://blog.alexw.net/2016/09/02/%E8%A3%BD%E4%BD%9C-win10-sysprep-answer-file/

https://technet.microsoft.com/en-us/library/hh825072.aspx

https://technet.microsoft.com/en-us/library/hh824910.aspx

 

Init EFI protected partition

http://www.winability.com/delete-protected-efi-disk-partition/

diskpart

select disk #

list partition

select partition #

clean

 

廣告

win10 battery drained so fast unexpectedly, Dell Inspiron 15-5559

http://wp.me/ph3BR-1GA

 

this is really pain in the ass and problem encountered.

what had happened, PC problem or Win10 problem ?! god knows.

This PC went to sleep but auto wake up and so report the battery is so low but will not boot, repeatable.

or pushed power button then over night, the battery is completely drained, also no boot, occasional & repeatable.

shutdown the machine but no into sleep mode, the battery is safe without overnight drained issue, but still some leakage about 10% overnight. The battery report generation mechanism has wrong, or really the PC hardware fault, or Win10 bug ?! you tell.

We are waiting for problem solving & solution, but who care this at Microsoft or at Dell, at least need someone who is really capable to understand such circumstance, otherwise, so many calls for customer care, it does not help at all.

This is really the case a notebook no longer mobile, it must stay at power plug and never wanted goes to sleep mode, or perhaps a more fancy term, hibernation mode.

waiting…….

perhaps a very single case really ?!

 

dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem
dell_15-5559_battery_problem

 

 

This is really a problem of win10 with this PC to an ordinary user, they bought and uses as daily basis but who is incapable to address such detail until battery drained, and panic on boot failure & recovery story, but so far Dell has no any recommendation or to advise solution, perhaps they are hardware seller-only and will not be looking at such hard-soft mixture issue to a solution actively. so pray and works on the own, and workaround is here seems to work at the moment.

How to do that,

1) turn OFF or de-select fast startup boot mode;
2) manually enable hibernate mode;
3) change power setting to enforce PC shutdown, at monitor folding or a push to power button;

power setting_workaround

These would help user to really shutdown their laptop but to forgot habit & user friendly experience with win7/win8. It also helping the user is no longer be able to put their laptop in such a funny state without notifying battery drained.

Registry key,

Win10 Fast Startup is disabled, a workaround

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled = 0x0000

 

Win10 Fast Startup is enabled, problematic with this PC

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled = 0x0001

 

validation done, battery power has been ceased to drain out completely over a night.power setting_workaround_result

 

 

 

turn OFF Fast Startup


REM run this bat file as administrator

@echo off

:: Created by: Shawn Brink
:: http://www.tenforums.com
:: Tutorial: http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

:: To turn off Fast Startup
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /V HiberbootEnabled /T REG_dWORD /D 0 /F

 

turn ON Fast Startup


@echo off
REM run this bat file as administrator
:: Created by: Shawn Brink
:: http://www.tenforums.com
:: Tutorial: http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

:: To enable hibernate
powercfg -h on

:: To turn on Fast Startup
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /V HiberbootEnabled /T REG_dWORD /D 1 /F

 

REF:

http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

http://en.community.dell.com/support-forums/laptop/f/3518/p/19682780/20902850?rfsh=1461382560604

http://bbs.pigoo.com/forum.php?mod=viewthread&tid=60415&page=1#pid730104

Win10 Dell Insprion 15-5559 battery report and performance rating

win10 performance rating,

open powershell as adminstrator, run

get-wmiobject -class win32_winSAT

 

win10_rating

 

 

 

Battery report

COMPUTER NAME GEORGER-DELL
SYSTEM PRODUCT NAME Dell Inc. Inspiron 5559
BIOS 1.1.6 01/12/2016
OS BUILD 10586.212.amd64fre.th2_release_sec.160328-1908
PLATFORM ROLE Mobile
CONNECTED STANDBY Not supported
REPORT TIME 2016-04-20 15:09:43

Installed batteries

Information about each currently installed battery

BATTERY

1

NAME DELL 78V9D5A
MANUFACTURER Panasonic
SERIAL NUMBER 3315
CHEMISTRY LION
DESIGN CAPACITY 41,440 mWh
FULL CHARGE CAPACITY 37,873 mWh
CYCLE COUNT

Recent usage

Power states over the last 3 days

START TIME STATE SOURCE CAPACITY REMAINING
2016-04-18 06:43:57 Active AC 110 % 41,440 mWh
09:20:30 Suspended 110 % 41,440 mWh
10:53:43 Active Battery 98 % 36,615 mWh
11:18:49 Active AC 87 % 32,708 mWh
11:44:00 Suspended 99 % 36,956 mWh
11:48:22 Active AC 99 % 37,311 mWh
12:30:00 Suspended 110 % 41,440 mWh
12:37:46 Active AC 110 % 41,440 mWh
13:00:00 Suspended 110 % 41,440 mWh
14:33:23 Active AC 110 % 41,440 mWh
14:54:00 Suspended 110 % 41,440 mWh
14:59:41 Active AC 110 % 41,440 mWh
16:06:00 Suspended 110 % 41,440 mWh
16:12:04 Active AC 110 % 41,440 mWh
18:00:00 Suspended 110 % 41,440 mWh
18:03:23 Active AC 110 % 41,440 mWh
18:04:56 Suspended 110 % 41,440 mWh
18:11:24 Active AC 110 % 41,440 mWh
18:17:00 Suspended 110 % 41,440 mWh
22:41:57 Active AC 110 % 41,440 mWh
23:49:00 Suspended 110 % 41,440 mWh
23:52:37 Active AC 110 % 41,440 mWh
23:52:37 Suspended 110 % 41,440 mWh
23:54:34 Active AC 110 % 41,440 mWh
2016-04-19 00:16:00 Suspended 110 % 41,440 mWh
00:23:21 Active AC 110 % 41,440 mWh
10:09:07 Suspended 110 % 41,440 mWh
10:17:37 Active AC 110 % 41,440 mWh
10:35:00 Suspended 110 % 41,440 mWh
10:37:38 Active AC 110 % 41,440 mWh
19:11:00 Suspended 110 % 41,440 mWh
19:16:01 Active AC 110 % 41,440 mWh
19:16:22 Suspended 110 % 41,440 mWh
23:18:01 Active AC 110 % 41,440 mWh
23:30:00 Suspended 110 % 41,440 mWh
23:32:22 Active AC 110 % 41,440 mWh
23:38:00 Suspended 110 % 41,440 mWh
23:42:05 Active AC 110 % 41,440 mWh
2016-04-20 00:54:00 Suspended 110 % 41,440 mWh
00:57:13 Active AC 110 % 41,440 mWh
00:57:13 Suspended 110 % 41,440 mWh
01:01:40 Active AC 110 % 41,440 mWh
01:13:00 Suspended 110 % 41,440 mWh
01:15:29 Active AC 110 % 41,440 mWh
02:09:42 Suspended 110 % 41,440 mWh
02:11:29 Active Battery 99 % 37,089 mWh
02:11:29 Suspended 99 % 37,089 mWh
08:50:54 Active Battery 94 % 35,283 mWh
08:50:54 Suspended 94 % 35,283 mWh
08:51:29 Active Battery 94 % 35,150 mWh
13:22:42 Suspended 5 % 2,042 mWh
15:07:24 Active Battery 4 % 1,598 mWh
15:09:00 Report generated Battery 4 % 1,465 mWh

Battery usage

Battery drains over the last 3 days

 

START TIME STATE DURATION ENERGY DRAINED
2016-04-18 10:53:43 Active 0:25:05 10 % 3,907 mWh
02:11:29 Active 0:00:00
08:50:54 Active 0:00:00
08:51:29 Active 4:31:12 88 % 33,108 mWh
15:07:24 Active 0:01:35 133 mWh

Usage history

History of system usage on AC and battery

BATTERY DURATION AC DURATION
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2015-12-07

– 2015-12-14

3:33:37 7:08:29
2015-12-14

– 2015-12-21

11:26:25 38:51:14
2015-12-21

– 2015-12-28

6:34:43 8:28:32
2015-12-28

– 2016-01-04

20:22:51 56:22:04
2016-01-04

– 2016-01-11

26:09:38 77:12:04
2016-01-11

– 2016-01-18

1:31:02 10:33:39
2016-01-18

– 2016-01-25

30:03:52 108:57:05
2016-01-25

– 2016-02-01

1:46:49 13:06:32
2016-02-01

– 2016-02-08

4:10:37 11:53:43
2016-02-08

– 2016-02-22

7:32:48 16:32:59
2016-02-22

– 2016-02-29

3:07:36 20:40:46
2016-02-29

– 2016-03-07

4:46:18 9:46:55
2016-03-07

– 2016-03-14

2:50:21 19:00:23
2016-03-14

– 2016-03-21

3:29:58 9:40:34
2016-03-21

– 2016-03-28

1:25:33 15:10:13
2016-03-28

– 2016-04-04

6:28:18 11:52:29
2016-04-04

– 2016-04-11

1:15:29 21:04:24
2016-04-12 10:03:30
2016-04-13 1:18:59
2016-04-14 0:17:05 1:44:06
2016-04-15 4:02:30
2016-04-16 2:41:59
2016-04-17
2016-04-18 0:25:04 8:39:46
2016-04-19 8:43:32

Battery capacity history

Charge capacity history of the system’s batteries

PERIOD FULL CHARGE CAPACITY DESIGN CAPACITY
2015-12-07

– 2015-12-14

40,330 mWh 41,440 mWh
2015-12-14

– 2015-12-21

40,351 mWh 41,440 mWh
2015-12-21

– 2015-12-28

39,264 mWh 41,440 mWh
2015-12-28

– 2016-01-04

39,908 mWh 41,440 mWh
2016-01-04

– 2016-01-11

39,605 mWh 41,440 mWh
2016-01-11

– 2016-01-18

38,302 mWh 41,440 mWh
2016-01-18

– 2016-01-25

39,225 mWh 41,440 mWh
2016-01-25

– 2016-02-01

38,169 mWh 41,440 mWh
2016-02-01

– 2016-02-08

38,102 mWh 41,440 mWh
2016-02-08

– 2016-02-22

38,035 mWh 41,440 mWh
2016-02-22

– 2016-02-29

37,903 mWh 41,440 mWh
2016-02-29

– 2016-03-07

37,816 mWh 41,440 mWh
2016-03-07

– 2016-03-14

37,700 mWh 41,440 mWh
2016-03-14

– 2016-03-21

37,648 mWh 41,440 mWh
2016-03-21

– 2016-03-28

37,604 mWh 41,440 mWh
2016-03-28

– 2016-04-04

37,585 mWh 41,440 mWh
2016-04-04

– 2016-04-11

37,530 mWh 41,440 mWh
2016-04-12 37,503 mWh 41,440 mWh
2016-04-13 37,503 mWh 41,440 mWh
2016-04-14 37,503 mWh 41,440 mWh
2016-04-15 37,503 mWh 41,440 mWh
2016-04-16 37,503 mWh 41,440 mWh
2016-04-17 37,503 mWh 41,440 mWh
2016-04-18 37,503 mWh 41,440 mWh
2016-04-19 37,503 mWh 41,440 mWh

Battery life estimates

Battery life estimates based on observed drains

AT FULL CHARGE AT DESIGN CAPACITY
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2015-12-07

– 2015-12-14

4:09:42 4:16:35
2015-12-14

– 2015-12-21

3:42:57 3:48:58
2015-12-21

– 2015-12-28

3:49:28 4:02:12
2015-12-28

– 2016-01-04

3:39:04 3:47:29
2016-01-04

– 2016-01-11

3:44:06 3:54:29
2016-01-11

– 2016-01-18

3:56:46 4:16:10
2016-01-18

– 2016-01-25

3:42:57 3:55:33
2016-01-25

– 2016-02-01

3:26:12 3:43:52
2016-02-01

– 2016-02-08

4:17:27 4:40:00
2016-02-08

– 2016-02-22

4:16:01 4:38:57
2016-02-22

– 2016-02-29

3:42:19 4:03:04
2016-02-29

– 2016-03-07

3:38:14 3:59:09
2016-03-07

– 2016-03-14

3:43:39 4:05:50
2016-03-14

– 2016-03-21

4:06:37 4:31:27
2016-03-21

– 2016-03-28

3:52:54 4:16:40
2016-03-28

– 2016-04-04

4:24:43 4:51:52
2016-04-04

– 2016-04-11

4:21:08 4:48:21
2016-04-12
2016-04-13
2016-04-14 4:20:45 4:48:07
2016-04-15
2016-04-16
2016-04-17
2016-04-18 4:00:36 4:25:52
2016-04-19

Current estimate of battery life based on all observed drains since OS install

Since OS install 3:41:05 4:01:55

 

 

Win 10, FUJITSU SH560, battery report and AHCI bug fix

http://wp.me/ph3BR-1Eq

 

WIN10, FUJITSU SH560

這種機器有點怪, 原生成是WIN7, SATA 硬碟, 會計的項目經理們在中國內地買的, 幾個帶來就放在當地用, 出差不再需要帶電腦過去. 但有個怪現象, 休眠後會起不來, 必須拔電池, BIOS 的日期也會跑掉, 錯誤以為BIOS電池失效, 結果也不是. BIOS 裡面開了 IDE, 不支援 AHCI, 結果重設 BIOS 開機就死機藍畫面 STOP 0x0000007B INACCESSABLE_BOOT_DEVICE, 這是第二次遇到類似的問題, 成因不明, 買來的機器就這樣.

曾經請教過人家, 估計都是 OS / BIOS 造成的, 所以管不上了, 只有禁止休眠, 限定用 IDE 模式, 就一直用了四五年了, 很好. 最近經理們收到微軟通知, [不小心] 按了同意了自動更新到WIN10. 結果, 有的死機, 有的就好好. 依稀記得曾經處理過有成功的案例, 所以活動一下, 順到看看他們的老機器跑WIN10如何.

FUJITSU SH560 休眠後無法啟動, 要拔電重開, http://bbs.pigoo.com/thread-54437-1-1.html

Win10, IDE 模式底下安裝, ACHI 模式底下會死在循環重啟, http://bbs.pigoo.com/thread-59486-1-1.html

微軟的 STOP 0x0000007B INACCESSABLE_BOOT_DEVICE 解釋, https://support.microsoft.com/zh-tw/kb/922976 (微軟這個沒有勘誤, 重複的兩個字段), 修改以下兩個機碼,

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV

在右側窗格中,在 [名稱] 欄中的 [Start] 上按右鍵,然後按一下 [修改]。
在 [數值資料] 方塊中,輸入 0,然後按一下 [確定]。
在 [檔案] 功能表上,按一下 [結束] 以關閉登錄編輯程式

 

如果想懶惰, 也可以參考這篇, http://wp.me/ph3BR-1hI, 直接寫好劇本, 然後匯入到 WIN 10, 不需要REGEDIT手動編輯,


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci]
"Start"=dword:00000000

 

備份原有的 REGISTRY的 BATCH FILE, 只能在修改前執行一次, 一或二或三個機碼

@echo off

echo By Xiaolaba, last update, 2016-MAR-12
echo for win8 / win 8.1 / win 10, backup registry for two or three keys followings,
echo HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
echo HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
echo HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride


SET mypath=%~dp0

SET file_name1=reg_Msahci_Acer5830.txt
SET file_name2=reg_IastorV_Acer5830.txt
SET file_name3=reg_storahci_StartOverride_Acer5830.txt

@echo.

regedit /e "%mypath%%file_name1%" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
regedit /e "%mypath%%file_name2%" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
regedit /e "%mypath%%file_name3%" HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride

@echo backup keys now... done!
echo %mypath%%file_name1%
echo %mypath%%file_name2%
echo %mypath%%file_name3%

@echo.

echo You can modify registry, set OS to AHCI mode, and then enable ACHI in BIOS,
echo STOP 0x0000007B INACCESSABLE_BOOT_DEVICE will be solved during boot.

@echo.


pause

 

可是呢, 有些機器用這方法可以, 兩個 REG KEY 都存在, 改了就好了. 但是有些呢, 備份的結果是只有一支KEY存在, 例如,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV

但是另外一支KEY不存在, 例如,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci

 

結果是用 SAFE MODE 進入 WIN10 也沒辦法解決, 但是並沒有藍屏STOP 0x0000007B, 症狀就只看到WIN10啟動時的特徵的那塊 “田", 然後就是說故事, 從前有個公公…….BOIS切回 IDE 模式就可以繼續操作那塊 “田". 紀錄嘗試用 BCD 的方法, BCDEDIT 是編輯開機設定資料 (BCD) 檔案提供一個存放區的工具,

WIN10 進入 SAFE MODE, 要 REBOOT,
bcdedit /set {current} safeboot minimal

WIN10 退出 SAFE MODE, 要 REBOOT,
bcdedit /deletevalue {current} safeboot

https://technet.microsoft.com/zh-tw/library/cc709667%28v=ws.10%29.aspx

結果還是不行, 那剩下最後一個了, 刪除另外一個 REGSITRY KEY, 如下

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride

或者用一個 BATCH FILE做這個工作, 內容如下,

reg delete “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride" /va /f

也可以用 REG 檔案匯入的方法, REG 檔案內容如下,

Windows Registry Editor Version 5.00

[-KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride]

 

這下最後成了. 完畢.

 

另外看看電池的報表, 更新了自動劇本如下,


@echo off

echo By Xiaolaba, win8 / win 8.1 / win 10, battery status report generation script.
echo last update, 2016-01-19
@echo.

mkdir battery_log

set file_name=.\battery_log\battery_log_%date%_%time:~0,2%%time:~3,2%%time:~6,2%.html

echo battery log file = %file_name%
powercfg /batteryreport /output %USERPROFILE%\Desktop\%file_name%



rem pause 1 second, await html generation
rem @ping 127.0.0.1

start .\battery_log\battery_log_%date%_%time:~0,2%%time:~3,2%%time:~6,2%.html

@echo.
rem pause

SH560_WIN10_battery_log1
SH560_WIN10_battery_log1
SH560_WIN10_battery_log2
SH560_WIN10_battery_log2

Win 10, battery report wrong time stamp during suspend and wake up

http://wp.me/ph3BR-1D7

 

最新的發現, 很奇怪, 不知道是 WIN10的BUG還是 ASUS 的 BUG. 好幾次看到詭異的現象. 電池報告, 報告表頭是寫當下的時間例如早上9點, 但是報告內容顯示報告生成的時間卻是凌晨3點? 都說過了, WIN8或WIN10的電腦, 不知道三更半夜鬼鬼祟祟自動起來幹點啥的, 無人知曉, 重點是這份報告明顯有瑕疵. 休眠後常出現這現象.

要複製這個現象, 用一個 BATCH FILE  (BAT 檔案) 比較好操作, 這個 BAT 檔案, 每一行都是基本動作, 有了這個小工具, 不難發現這樣重複出現的BUG.

 

BAT 檔案的內容和執行的動作如下,

向WIN10系統拿到現在年月日時分秒, 作為電池報告的檔案名稱, 格式是 html, 就是網頁的格式. 例如, battery_log_2016-01-10225053.html

然後啟動電池報告, 結果輸出到上面指定的那個檔案, 存儲在你的桌面上.

最後開啟這個報告, 瀏覽器會看到類似的畫面和資料.

win10 battery report time error
win10 battery report time error
win10 battery report time error
win10 battery report time error

 

 

這個BAT的內容如下, 剪貼到記事本, 存到桌面, 名稱改為 battery_log.bat.

點擊兩下就會看到你的電腦裡面的電池報告.


@echo off

echo By Xioalaba, win8 / win 8.1 / win 10, battery status report generation script.
echo last update, 2016-01-19
@echo.

set file_name=battery_log_%date%%time:~0,2%%time:~3,2%%time:~6,2%.html

echo battery log file = %file_name%
powercfg /batteryreport /output %USERPROFILE%\Desktop\%file_name%

start battery_log_%date%%time:~0,2%%time:~3,2%%time:~6,2%.html

@echo.
pause

REF:
http://wp.me/ph3BR-1mX
https://goo.gl/rvPvDs

PL2303, Win8.1 ok but Win10 error code 10 again ?

http://wp.me/ph3BR-1CR

 

前年遇到鳥事, 以為知道了原因, 也解決了. 後來建議用家都買USB轉COM (或者稱為USB轉RS232) 的線, 必須要確認支援 WIN 8.1 的, 所以這個不幸, 那個不行的噪音就消失了一陣子, 直到2014年十月, FTDI為了同樣打擊盜版IC的理由, 在微軟AUTO UPDATE, 使用DRIVER UPDATE的手段, 把所有認為偵測到是盜版IC在裡面的USB PID 改成 0x0000, 一堆人的機器, 只要用FTDI (盜版IC ?!) 的都突然掛掉, 那買成品裡面包了一個IC的哪知道是盜版還是原廠呢 ? 基本是怨聲載道, 後來 FTDI 移除那兩個 DRIVER UPDATE, 微軟做了甚麼工作避免類似事情就不得而知了.

最近大家都換 WIN 10的電腦, 原來那些在 WIN 8.1 用的好好的 USB 轉 COM, 又來出事了, 這次看看, 還是PL2303, 確定 WIN8.1 是完全沒問題的, 證明用家有聽建議, 隨便插隨便用, 但是在 WIN10 裡面, 也隱藏起來, 一般用家還不知道怎樣看給你個感嘆號,ERROR 10.

這檔事情的原因不明, 解決辦法還是嘗試用那個舊版的驅動程式, 結果驅動成功, 不過每次拔除後要再選一次, 沒空給他試了, 到底盜版IC還是原廠的? 微軟搞飛機還是那些晶片廠和驅動程式搞飛機 ? 拭目以待. 所以, 暫時給用家的建議, 買一條, WIN 10 專用的, 指定不要 PL2303, 也不要 FTDI, CH340的還好, 起碼驅動安裝上了, 就不會每次 “打擊盜版" 在亂改, CP2102的也可以. 暫時解決自己面對的客戶問題最重要. 難道還是一堆人買到盜版晶片, WIN8.1得了 ? 那之前那篇的推論就真的呈現了. 但是原廠或盜版的, 過了保固時效也不鳥你, 就一律不能用就對了, 那用盜版和原廠的分別在哪裡?!

PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem
PL2303 win10 error 10, driver problem

 

 

REF:

http://www.ftdichip.com/Support/Utilities.htm

Watch That Windows Update: FTDI Drivers Are Killing Fake Chips

http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/