Acer predator Helios 300 Intel ssd (intel ssdpekkw256g7) 1803 build Microsoft fix out!

geekromi
geekromi Member Posts: 144 Skilled Fixer WiFi Icon
edited November 2023 in 2018 Archives
Just to let you know, Microsoft, on May 25, launched a fix-update to resolve the problem on build 1803 related on machines equipped with intel ssd (intel ssdpekkw256g7): it's called KB100403 and I really hope that will fix the issue  about crashing when unplugged !

Answers

  • geekromi
    geekromi Member Posts: 144 Skilled Fixer WiFi Icon
    edited June 2018
     

    Update: the right update number is KB4100403 , (digit error)
  • szopin
    szopin Member Posts: 11

    Tinkerer

    Anyone managed to get that installed? Windows update is bricked thanks to Acer blocking the original 1803 update and manually downloading from MS http://www.catalog.update.microsoft.com/Search.aspx?q=KB4100403 does not work (from the name it seems you need to first need to get to 1803 to apply this fix)

  • geekromi
    geekromi Member Posts: 144 Skilled Fixer WiFi Icon
    szopin said:
    Anyone managed to get that installed? Windows update is bricked thanks to Acer blocking the original 1803 update and manually downloading from MS http://www.catalog.update.microsoft.com/Search.aspx?q=KB4100403 does not work (from the name it seems you need to first need to get to 1803 to apply this fix)


    Hi szopin, that's funny is'nt it?, as far as I know, after realizing that the upgrade to build 1803 was creating issues with Intel ssd (and Toshiba too), Microsoft blocked the upgrade on machines Intel P600 series-equipped  (intel ssdpekkw256g7), but now, that they have realized the fix update KB4100403, we should have the possibility to install the 1803 build first and then the fix: Why is the 1803 build still blocked  for Intel ssd equipped computers?

  • milsabords
    milsabords Member Posts: 9

    Tinkerer

    1803 installed w/o problem on my Predator 300. I tried to dl and install KB4100403 ... it failed.
  • szopin
    szopin Member Posts: 11

    Tinkerer

    1803 installed w/o problem on my Predator 300. I tried to dl and install KB4100403 ... it failed.
    Today, or before they blocked it? Are you sure you have the impactred ssd that was blocking it? It still fails here
  • geekromi
    geekromi Member Posts: 144 Skilled Fixer WiFi Icon
    szopin said:
    1803 installed w/o problem on my Predator 300. I tried to dl and install KB4100403 ... it failed.
    Today, or before they blocked it? Are you sure you have the impactred ssd that was blocking it? It still fails here

    there's something weird here: I will give it a try and let you know, actually after having issues with my intel ssd, when build 1803 came out, i decided to roll back to 1709, now, I hope to have the possibility, to re-update to 1803 and then applying the KB4100403 fix!
  • HiWayKiller
    HiWayKiller Member Posts: 19 Troubleshooter
    Able to update the Microsoft Knowledge Base without any hassle.
  • geekromi
    geekromi Member Posts: 144 Skilled Fixer WiFi Icon
    edited June 2018
    Update: I tried to update windows from 1709 to 1803 and the operation  was concluded successfully, but after all , windows said that no further updates were avalaible: so what about the KB4100403?, well , I went to have a look into installed programs tab in control panel and looking at installed updates, i found it,  that means that the fixing update has been installed with no problems: then I tried using the pc just on battery and the computer went on working flawlessy for all the time, (when I was on 1803 just came out, the system, when unplugged, used to crash after only few minutes).
    So, at the moment the issue seems to be fixed,  anyway, I will let you know for further news.
  • milsabords
    milsabords Member Posts: 9

    Tinkerer

    Before they blocked. My SSD is Intel SSDPEKKW256G7.
    szopin said:
    1803 installed w/o problem on my Predator 300. I tried to dl and install KB4100403 ... it failed.
    Today, or before they blocked it? Are you sure you have the impactred ssd that was blocking it? It still fails here