Samsung ATIV Smart PC 500T 8.1 Update

Anonymous
2013-10-30T00:16:35+00:00

Currently, after the 8.1 update, Internet Explorer doesn't work, office is slow, the desktop is slow, and I have a whole host of other problems. Samsung says I need to pay $40 to reimage, but the only reason I updated was because it said this device is compatible at this web address: http://www.microsoftstore.com/store/msusa/en\_US/pdp/Samsung-ATIV-Smart-PC-500T-Tablet-White/productID.265664500.

Both Microsoft and Samsung refuse to refund the $40 charge that is necessary to make my computer work again, and I cannot access the recovery partition on my Samsung device. It is there, just not accessible. Anyone who has information on how to solve this issue, if you could give me an answer it would be greatly appreciated.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-06-19T19:49:14+00:00

I started my own thread trying to get this resolved and sent an email to realtek.

http://answers.microsoft.com/en-us/windows/forum/windows8\_1-hardware/samsung-500t-microsoft-update-broke-sound/9f994966-978f-4cdd-a8b4-629abc503f1c?tm=1434678495366

I have researched the way drivers are handled a little bit and since this driver will work until its time to reboot, I have been disabling the device in device manager before shutting the tablet down, then after booting up I enable it again, this has allowed to to function but is a pain. But that being said drivers are handle in a couple of different ways, some are loaded as the system is initializing and some are as plug and play  (or loaded on demand) after the system is booted up. It seems to me that this driver can function as plug and play since that is what I am doing manually through device manager, if someone could write the configuration file for the driver to operate like that it might solve the issue.

Anyone know how to do that?

************************************************************************

So to be clear: It is a driver configuration error, the driver for the realtek hardware is causing the system to hang during boot.

If your system is hanging, you must restart in safe mode, then go to device manager and disable to the realtek sound device. Then reboot in normal mode and again enable the sound device, thendo not shut down the tablet unless you disable the sound device first.

I keep the tablet in sleep mode when I am not using it, it will wake up fine, but if you shut it down without disabling you will have to do the safe mode thing again. Until they fix the driver this is the only way to have the tablet function with sound.

Was this answer helpful?

6 people found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Newest
  1. Anonymous
    2015-04-27T18:13:21+00:00

    Jacob W. Klein 

    Your detailed response is excellent, and spot on to what I experienced with my Samsung ATIV XE500T1C-HA1US.  I even tried it again this weekend...and wasted way too many hours, but because of your observations, I can at least get 8.1 installed.

    Have you experienced an issue with 8.1 giving the Blue Screen of Death after one of the latest 8.1 updates if the input power cable it plugged in?  I had to roll back to Windows 8 again just because of this issue.  I can't pinpoint which 8.1 update started this issue, and tried uninstalling the latest 30 updates, nothing worked.  The tablet works fine when unplugged, but as soon as it's plugged in, it crashes.  I'm hoping it is just my one particular tablet, or Input Power cable.

    I wonder if there is a generic audio driver that can pick up on any speaker hardware on a Windows 8-8.1 OS?  Or, perhaps I can bypass the tablet speakers and export via Bluetooth to an external speaker? 

    Sheshanarayana Ravishankar -  Thank you for your attempt, but Jacob is correct, the issue is directly related to the Realtek Audio driver and 8.1.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-27T12:16:39+00:00

    jguzek wrote, on April 20, 2015:

    As others have mentioned,   the only way I was able to upgrade to 8.1 was to uninstall the realtek audio drivers,  and leave them uninstalled.    8.1 works fine as long as I leave the audio drivers disabled.

    When I install and enable sound the device hangs at boot-up.

    So thus far,   I've learned to live without sounds.   Only other option at this point is to downgrade back to 8.0.

    I even attempted to install old driver versions, but the results are the same.

    Come on Samsung/Microsoft,   help us out here!

    ================================================

    Jacob W. Klein wrote, on April 26, 2015:

    This is exactly the behavior I am noticing, on my Samsung ATIV XE500T1C-HA1US.

    On a fresh Windows 8 install (using "Reset my PC"), with all Windows Updates installed, and with all updates from "SW Update" updated... the Windows 8.1 upgrade would fail with error code: "0xC1900101 - 0x40017" with a blue light that was flashing off about every second, coinciding with a subtle "tick" sound ticking every second, from near the front camera.

    But if I first uninstalled RealTek software from Control Panel's "Programs and Features", then it would upgrade to Windows 8.1 successfully. But then, when running Windows 8.1, if I install "Sound Driver" from Samsung "SW Update", I'll get sound, but any reboot will hang. The only way to recover is to hold the power button down while the boot is hung, until you can get to prompts to use System Restore.

    Basically, the problem is:

    Samsung "SW Update" currently (4/26/2015) offers:

    - "Sound Driver" Ver 6.2.9200.31202 on Windows 8

    - "Sound Driver" Ver 6.2.9200.34712 on Windows 8.1

    ... and having either installed will cause an upgrade to Windows 8.1 to fail, and will also cause booting to hang on Windows 8.1.

    If you are wanting Windows 8.1, the only workaround is to not have sound drivers installed when you do the upgrade, and then do not install them after the upgrade.... meaning you won't have any sound in Windows 8.1.

    I have chatted with agents on Samsung Live Chat, and I encourage any Samsung customers affected by the issue to do the same. One of the agents I chatted with took my info, and filed a "technical transaction" to their higher-ups, so we'll see how that goes.

    In the meantime, this device has Windows 8.1, but no sound. I'm not sure if fault lies with RealTek, or Microsoft, or Samsung ... but I have isolated the cause as much as I could.

    Can anyone fix this?

    Sheshanarayana:

    Your information is not helpful, towards solving this problem.

    Please thoroughly read the detailed analysis that I have provided, and pass along the information to someone who can provide a "Realtek I2S Audio Codec" driver for a Samsung ATIV XE500T1C-HA1US for Windows 8.1, that doesn't make the system hang at bootup.

    We do not need general solutions from a script, or guesswork. We've already done the analyses, and spent countless hours figuring out the details for you. We now need Microsoft or Samsung to step up, and figure out more details for us.

    ::clearly frustrated::

    • Jacob

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-27T07:37:41+00:00

    Thank you for your response.

    I apologize for the inconvenience cause. Due to some technical issues, the article provided in my previous response did not get reflected properly.

    I would request you to follow the methods and links below:

    Method 1:

    Set Internet Explorer as default web browser and then try to update Samsung Ativ Pro 500T.

    Make Internet Explorer your default browser

    http://windows.microsoft.com/en-US/internet-explorer/make-ie-default-browser#ie=ie-11

    Method 2:

    If still the issue persists, try reinstalling the Samsung Ativ Pro 500T drivers and check if the issue persists

    Manually disconnect the device from the computer

    and then try removing/uninstalling it.

    If this device is still connected to the computer, disconnect it manually from the computer and then try uninstalling its drivers from the Device Manager or try removing it from the “Device” section in “PC Settings”. You may follow these steps to uninstall the driver from the Device Manager.

    a)      Press “Windows Logo” + “X” keys on the keyboard.

    b)     Click on “Device Manager”.

    c)      Search for the device that you would like to remove from the computer.

    d)     Right click on it and select “Uninstall”.

    e)     Follow the on-screen instructions and restart the computer, if prompted.

    If this did not help, then try the next method to check if this device driver is present in “Programs and Features” and if present, then uninstall it from there.

    Method 3:

    Check if the Device Driver software is present in the “Programs and Features”

    a)      Press “Windows Logo” + “X” keys on the keyboard.

    b)      Select “Programs and Features” from the menu.

    c)      In the “programs and Features” window, check if the device driver software is present in the program list.

    d)      If present, then click on it and select “Uninstall”.

    e)       Follow the on-screen instructions and restart the computer, if prompted.

    in order to Re-installing Drivers I would suggest you to contact computer manufacture provided link below.

    http://www.verizonwireless.com/search/vzwSearch?Ntt=Ativ%20Pro%20drivers&nav=Global&gTab=undefined

    Hope the information helps. Keep us updated about the status of the issue persists. We will be happy to help.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-04-27T03:09:27+00:00

    As others have mentioned,   the only way I was able to upgrade to 8.1 was to uninstall the realtek audio drivers,  and leave them uninstalled.    8.1 works fine as long as I leave the audio drivers disabled.

    When I install and enable sound the device hangs at boot-up.

    So thus far,   I've learned to live without sounds.   Only other option at this point is to downgrade back to 8.0.

    I even attempted to install old driver versions, but the results are the same.

    Come on Samsung/Microsoft,   help us out here!

    This is exactly the behavior I am noticing, on my Samsung ATIV XE500T1C-HA1US.

    On a fresh Windows 8 install (using "Reset my PC"), with all Windows Updates installed, and with all updates from "SW Update" updated... the Windows 8.1 upgrade would fail with error code: "0xC1900101 - 0x40017" with a blue light that was flashing off about every second, coinciding with a subtle "tick" sound ticking every second, from near the front camera.

    But if I first uninstalled RealTek software from Control Panel's "Programs and Features", then it would upgrade to Windows 8.1 successfully. But then, when running Windows 8.1, if I install "Sound Driver" from Samsung "SW Update", I'll get sound, but any reboot will hang. The only way to recover is to hold the power button down while the boot is hung, until you can get to prompts to use System Restore.

    Basically, the problem is:

    Samsung "SW Update" currently (4/26/2015) offers:

    - "Sound Driver" Ver 6.2.9200.31202 on Windows 8

    - "Sound Driver" Ver 6.2.9200.34712 on Windows 8.1

    ... and having either installed will cause an upgrade to Windows 8.1 to fail, and will also cause booting to hang on Windows 8.1.

    If you are wanting Windows 8.1, the only workaround is to not have sound drivers installed when you do the upgrade, and then do not install them after the upgrade.... meaning you won't have any sound in Windows 8.1.

    I have chatted with agents on Samsung Live Chat, and I encourage any Samsung customers affected by the issue to do the same. One of the agents I chatted with took my info, and filed a "technical transaction" to their higher-ups, so we'll see how that goes.

    In the meantime, this device has Windows 8.1, but no sound. I'm not sure if fault lies with RealTek, or Microsoft, or Samsung ... but I have isolated the cause as much as I could.

    Can anyone fix this?

    Here is some possibly useful research:

    Was this answer helpful?

    0 comments No comments