[Windows 10] Update Windows 10更新後不能開機

否部電腦係Lenovo B50 ALL IN ONE,昨日更新完UPDATE後,每次開機都停留在LENOVO劃面上,不能進入WINDOWS:應該怎辦?謝謝!

試下用隻裝機碟或USB(用USB裝)
睇下是否可以救護.
若不能,
檔安有backup.
建議重裝!

TOP

Win 10正常啦

TOP

對BIOS嚟講係一般錯誤,去到UEFI嗰邊都會當咗係嚴重錯誤死畀你睇。
UEFI根本喺出錯誤之後嘅處理係做得仲衰過BIOS,BIOS一向Boot唔到預設要Boot嘅裝置都識得嘗試Boot其他裝置又可以畀人照樣入BIOS設定介面,但係UEFI一Boot唔到預設要Boot嘅裝置或者OS Loader就會死咗喺Logo畫面多數都唔畀人㩒鍵盤入UEFI設定介面。
呢個應該係UEFI嘅先天缺陷,除非所有底板廠合作重新整過一套新嘅UEFI標準同範本出嚟先解決到。

近年嘅IT界真係用行動證明咗「新野唔等如好野」。

TOP

否部電腦係Lenovo B50 ALL IN ONE,昨日更新完UPDATE後,每次開機都停留在LENOVO劃面上,不能進入WINDOWS: ...
dtses 發表於 2018-10-7 16:28


我情況同你一樣都係聯想廠机,搞咗我幾日,终於搞掂可以開机用windows 10,.
我解決方法係入底板設定關咗uefi,然後選擇auto.再重新開機就可以。

TOP

對BIOS嚟講係一般錯誤,去到UEFI嗰邊都會當咗係嚴重錯誤死畀你睇。
UEFI根本喺出錯誤之後嘅處理係做得仲衰 ...
Okt04175 發表於 2018-10-9 11:37



    你有冇了解過 UEFI 先呢? Spec 有晒全套 recovery 機制, 而市面上一般搵唔到 boot device 時會自動入 Setup 畫面.
https://www.uefi.org/sites/defau ... FI%20Spec%202_6.pdf
3.1.1 Boot Manager Programming
(......)
If any of the above-mentioned conditions is not satisfied, the next Boot#### in the BootOrder variable will be tried until all possibilities are exhausted. In this case, boot option recovery must be performed (see Section 3.4).

3.4 Boot Option Recovery
Boot option recovery consists of two independent parts, operating system-defined recovery and platform-defined recovery. OS-defined recovery is an attempt to allow installed operating systems to recover any needed boot options, or to launch full operating system recovery. Platform-defined recovery includes any remedial actions performed by the platform as a last resort when no operating system is found, such as the Default Boot Behavior (see Section 3.4.3). This could include behaviors such as warranty service reconfiguration or diagnostic options. In the event that boot option recovery must be performed, the boot manager must first attempt OS defined recovery, re-attempt normal booting via Boot#### and BootOrder variables, and finally attempt platform-defined recovery if no options have succeeded.

3.4.3 Boot Option Variables Default Boot Behavior
The default state of globally-defined variables is firmware vendor specific. However the boot
options require a standard default behavior in the exceptional case that valid boot options are not present on a platform. (......)
It is expected that this default boot will load an operating system or a maintenance utility. If this is anoperating system setup program it is then responsible for setting the requisite environment variables for subsequent boots. The platform firmware may also decide to recover or set to a known set of boot options.


樓主個 case 似停咗喺 load Windows 個階段多啲.

TOP

本帖最後由 Okt04175 於 2018-10-10 13:50 編輯

回覆 6# justiceice
我以前整一部3* Notebook嘅Windows嗰陣就係唔小心整壞咗OS Loader之後開機就死喺UEFI Logo度,仲要係㩒F2同Delete都唔肯入UEFI設定,最後要拆隻M2 SSD放落Desktop底板度格式化再整過Windows,呢種A2 Error以前行BIOS嘅底板Load唔入Windows係會Show咗Error Code一㩒掣就入到設定畫面。

咁樣應該要入邊個數?

TOP

本帖最後由 chue 於 2018-10-11 03:49 編輯

UEFI?同 WIN10 冇咩大關係,但可惜唔=同MS 冇關係,自從有左 UEFI 後裝野就麻煩左好多,因為有 SECURE BOOT,就算名義上關左都未必可以成功安裝用家想裝既 OS,最簡單例就係 LINUXLITE,永遠都裝唔入 PC

TOP

UEFI?同 WIN10 冇咩大關係,但可惜唔=同MS 冇關係,自得有左 UEFI 後裝野就麻煩左好多,因為有 SECURE BOOT,就 ...
chue 發表於 2018-10-11 01:51


回帶: https://www.hkepc.com/forum/redirect.php?goto=findpost&ptid=2419139&pid=37074077
Intel在2020年會停止支援UEFI class 0, 1, 2, 只會剩下class 3, Compatibility Support Module也會移除...
到時boot唔到XP啦...
仲要諗諗secure boot既證書發行者...

source:
http://www.guru3d.com/news-story/intel-halts-certain-uefi-bios-class-level-2-compatibility-modes-in-2020.html

quote from comments:
The Evil Empire, widely known as m$ is trying all that is possible to prevent/discourage people from using op systems other than window$ (and the "old", "obsolete" win versions too). One of the deceptive strategies is to persuade hardware manufacturers (that is, twisting their arms, bribing etc.) to come up with such "inventions" that would prevent (or make it more expensive) the use of, say Linux or/and iOS, as either only or primary or secondary OS within the same PC where window$ resides. Another benefit (for the Empire) is to make so-called cracking harder to implement (under a pretense of being concerned with the software's "safety").
Why (you may wonder)? Because that miserable, butterfly-looking pickpocket who owns m$ got obsessed with the idea of ruling the world, that's why...

   

There is still a bunch of OSes with no UEFI support, some old ones like XP some not that old. If csm is removed from the bios u won't be able to boot those OSes, period.
Then there is the "secure" boot mess.... "secure" boot makes it so only digitally signed code can be booted to. The problem here is that code has to be signed against a pre-installed certificate in the bios itself (installing custom certificates is usually locked out or very, very inconvenient) and the original owner of the certificates is MS. Is up to the mb manufacturers to include more certificates but they are not immune to external pressure, if Intel wants it, it can "convince" them to only ship X certificate or the chipset will be more expensive/refuse to work at all.
As an example, upon the release of UEFI a couple years ago, Ubuntu (a linux distribution) had to reach to MS to sign they own code..... that's a monopolistic, greedy and very dangerous situation that consumers should avoid at all costs.

TOP

自己送棺材比自己,ARM 陣營已經殺埋黎啦

TOP