Jump to content


please fix the windows 10 inaccessible device boot issue


  • Please log in to reply
25 replies to this topic

#1 Trial User_brad_*

Trial User_brad_*
  • Guests

Posted 02 November 2016 - 06:24 PM

Hi I purchased Alcohol 120 because i used the trial during my windows 7 days and since you stated that product is compatible with Windows 10, I skipped the trial version. unfortunately your latest version is broken. Per your support team, i am not the only one and you don't know how to fix it. so i paid $50.00 for a lifetime upgrade for a product that doesn't work. is there a way to request a refund?

 

thank you



#2 Trial User_Mike Jest_*

Trial User_Mike Jest_*
  • Guests

Posted 03 November 2016 - 12:00 PM

I have been a happy user for years.

 

I had Alcohol 120 running on my Asus Xenbook (model 501 UX) for about 4 years... Originally Windows 8.1, but upgraded to Windows 10 with no problems.

 

I bought a new Asus (Asus ROG GL502VS)...removed my license from the Xen (through the website)

 

Downloaded Alcohol 120 onto the ROG  started the install. It rebooted the computer, as is normal, Then Blue Screen. 

 

The ROG will not load any more... It is patched and current Windows 10 Home. There is a Current installation of Avast Pro. on the ROG, but other than that... it is completely new. 

 

Any help or suggestions?

 

Mike Jest

User since 2012



#3 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 03 November 2016 - 08:38 PM

This is apparently happening on systems that had older Alcohol version installed and then applied some Windows updates. Currently we are still not able to reproduce it on our test systems and we don't know how you may fix it but from the reports of other users that experienced this I can tell you that doing a Windows reset you should fix the problem and then be able to install Alcohol. It appears to be related to the Windows Anniversary update and as mentioned above is being looked into.

 

Please try the above or wait for a new version that will probably fix the problem.

You can also register in the forum and have access to the support forum section for the purchased users.

Topic moved to the appropriate forum section.



#4 Corsair63

Corsair63

    1% Member

  • Members
  • Pip
  • 1 posts

Posted 08 November 2016 - 09:11 PM

Same happens to me, since last version was working fine in my tablet and since last update not accesible disc is shown after trying to install.

 

and I have to licenses bought!! at teast is working in my desktop. :mad:



#5 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 09 November 2016 - 08:21 PM

You mean two licenses. :)

 

 

since last version was working fine in my tablet

 

You mean that the previous version worked and the latest one doesn't (on the same Windows 10(?) build)?



#6 maximino72

maximino72

    1% Member

  • Members
  • Pip
  • 2 posts

Posted 12 November 2016 - 04:51 PM

Hello, I can't install Alcohol on my pc with win10 anniversary update, when the pc boots the bsod appear with an error in stpd; I think the problem is v2.11.

Thanks.

#7 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 15 November 2016 - 08:10 PM

This is apparently happening on systems that had older Alcohol version installed and then applied some Windows updates. Currently we are still not able to reproduce it on our test systems and we don't know how you may fix it but from the reports of other users that experienced this I can tell you that doing a Windows reset you should fix the problem and then be able to install Alcohol. It appears to be related to the Windows Anniversary update and as mentioned above is being looked into.

 

Please try the above or wait for a new version that will probably fix the problem.



#8 maximino72

maximino72

    1% Member

  • Members
  • Pip
  • 2 posts

Posted 16 November 2016 - 11:57 AM

Latest version doesn't solve the problem. I will wait for a new version, hoping that it arrives asap.



#9 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 16 November 2016 - 09:35 PM

If the problem has to do with SPTD 2.11 we must wait until DuplexSecure releases a new version of SPTD to fix the problem. 



#10 uldim

uldim

    1% Member

  • Members
  • Pip
  • 2 posts

Posted 30 November 2016 - 03:19 PM

I have the same problem on the ASUS N552VW

Exist some fix or  patch????



#11 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 30 November 2016 - 08:38 PM

Not yet, please be patient.



#12 NARS

NARS

    Forum Administration

  • Administration
  • 2,775 posts

Posted 26 December 2016 - 10:53 AM

We have been trying to isolate this problem and we found that most of the users experiencing have systems with NVMe storage devices as boot device. Also it apparently only happens with the latest SPTD version. One system known to be affected is Surface Pro 4, our development team will soon get one for testing and trying to fix it.

 

In the mean time you may try to downgrade to an older Alcohol version.



#13 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,700 posts

Posted 27 December 2016 - 09:14 PM

Or downgrade to an older SPTD version.



#14 NARS

NARS

    Forum Administration

  • Administration
  • 2,775 posts

Posted 01 January 2017 - 05:32 AM

Yes, it should work :)  But not so easy... because as soon as you install latest Alcohol you get unbootable system :(



#15 uldim

uldim

    1% Member

  • Members
  • Pip
  • 2 posts

Posted 03 January 2017 - 10:16 PM

Yes I have an ASUN N551VW with an NVMe samsung hardisk

How can solve it???



#16 McKennaScole

McKennaScole

    1% Member

  • Members
  • Pip
  • 5 posts

Posted 05 January 2017 - 02:03 AM

I have the same problem. My laptop doesn't even boot into safe mode so I don't know what to do. I can't access my computer. Any solutions?

#17 NARS

NARS

    Forum Administration

  • Administration
  • 2,775 posts

Posted 05 January 2017 - 02:17 AM

You need to recover Windows to a working restore point. Then don't reinstall the latest Alcohol version until we release a new version that fixes this problem.



#18 McKennaScole

McKennaScole

    1% Member

  • Members
  • Pip
  • 5 posts

Posted 05 January 2017 - 07:12 AM

You need to recover Windows to a working restore point. Then don't reinstall the latest Alcohol version until we release a new version that fixes this problem.


I don't have a point to restore.

#19 McKennaScole

McKennaScole

    1% Member

  • Members
  • Pip
  • 5 posts

Posted 05 January 2017 - 11:47 AM

The problem seems to be Windows trying to boot into a drive other than the c: drive. It's not hard to guess that it thinks that the virtual drive of alcohol/sptd is the bootable one as this is caused by alcohol120. If someone can describe how to point c: drive as bootable using the command line of recovery I might be able to rescue without any cost



#20 McKennaScole

McKennaScole

    1% Member

  • Members
  • Pip
  • 5 posts

Posted 07 January 2017 - 03:41 AM

It's the latest sptd, not alcohol causing this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users