Windows 10: Dac not seen after Win 10 system image rollback (1607 fail to 1511)

Discus and support Dac not seen after Win 10 system image rollback (1607 fail to 1511) in Windows 10 Drivers and Hardware to solve the problem; I've had some 1511 to 1607 update "stuck" failures the past couple of weeks and have rolled back using a repair disk and a system image backup. The... Discussion in 'Windows 10 Drivers and Hardware' started by highstream, Jan 21, 2017.

  1. Dac not seen after Win 10 system image rollback (1607 fail to 1511)


    I've had some 1511 to 1607 update "stuck" failures the past couple of weeks and have rolled back using a repair disk and a system image backup. The thing that's happened afterward both times is that my dac, which is connected to a USB PCI sound card in my desktop computer, is not being seen by Windows Sound or in Device Mgr. OTOH, the NVIDIA and Reaktek drivers do show (as they should). Moving the USB cable to a mobo USB port gets the dac to show, but actual sound only plays for a brief moment (1 second) before stopping. I've tried to reinstall the dac's USB driver with it connected to the sound card, but it always gives an error message that the dac needs plugging in, which of course it already is. Replugging doesn't change that result. So I'm stuck.

    The first time this happened with Win 10 last week, I tried unplugging and replugging the USB connector here and there, disabling the other sound drivers, and rebooting a number of times, all without success. That is, until all of a sudden the dac appeared again as it should. It's as if it corrects itself by some kind of magic (same sense as when it occurred while reinstalling Win 8.1 a couple of years ago). And since last week it's remained ok until this morning, when after Windows tried an OS upgrade that hung, I rolled back via a system image. I've also tried Yamicsoft's Win 10 Mgr repair module, without success.

    What I'm trying to figure out is if there's some logic in the way Windows handles this that will allow me to get the dac recognized. Any ideas? Thanks,

    :)
     
    highstream, Jan 21, 2017
    #1
  2. Glenn234 Win User

    Rollback to Win 7 after Anniversary Update?

    I'm having so many problems with Win 10 version 1511 that I don't want to keep it.

    I'd like to try the new Anniversary edition (version 1607) to see if that solves the problems.

    However, if it still has too many problems, I'd like to rollback to the original Win 7.

    I know I can rollback from Win 10 Anniversary within 10 days.

    That will take be back to Win 10 version 1511.

    My question is AFTER that rollback to Win 10 version 1511,

    can I still rollback to the original Win 7 within 30 days

    of upgrading from Win 7 to Win 10 1511?

    In other words, will I be able to I do TWO rollbacks,

    or will upgrading from Win 10 1511 to Win 10 Anniversary

    wipe out the Win 7 rollback files.
     
    Glenn234, Jan 21, 2017
    #2
  3. //Windows 10 Update- System Backup Failed-9/4/2016

    Amrita Bhattacharjee - Tried the above as directed and it did not work, however learned a lot. When Task Manager is opened be sure to write down which software products were "enabled" before you "disable" them.

    I finally found a solution for my Dell XPS 8500 desktop to create a "System Image Backup" of Windows 10 version 1607. All of my attempted backups that failed were to replace a clean "System Image Backup" of Windows 10 version 1511. The new Windows 10 "System
    Image Backup" version 1607 is not compatible and will not replace a version 1511 "System Image Backup" and that was the problem. I changed the name of my version 1511 to "Temp" and the new Windows 10 version 1607 "System Image Backup" worked perfectly. I
    have since erased #2 External drive with version 1511 backup (that had failed to backup 1607) and it also backed up version 1607 perfectly.

    Hope this helps for future reference.

    Lameduck_9
     
    Lameduck2013, Jan 21, 2017
    #3
  4. sygnus21 Win User

    Dac not seen after Win 10 system image rollback (1607 fail to 1511)

    Hi, I have a DAC (Teac UD-503) connected to my Windows 10 Pro, X64-bit machine via USB so let's see if I can help. Questions...

    • What DAC is this?
    • Do you have the latest drivers for said DAC?
    • Are you connecting the DAC to the motherboard’s USB port?
    • Which Port – USB 3.0? USB 2.0?
    • In Playback devices (right click speaker icon, choose playback devices) is the DAC's device driver being shown?
    • Is the device driver set at the default playback device?
    • Under Device Manager - Sound, video and game controllers, does the DAC's driver show?
    I've got my DAC connected directly to the motherboard's USB 3.0 port and have never had any issues. Additionally, I've also got the DAC running through my SoundBlaster's ZXR soundcard via optical cable. My DAC allows for different connections and I just choose which driver I want to use via Playback Device. Anyway I mainly use USB, and as said, have never had issues.

    That said, perhaps answering those questions above my help solve your issue.

    Let us know.
     
    sygnus21, Jan 22, 2017
    #4
  5. Thanks for your reply. Sorry, I thought I had posted the solution here I came up with after a search around the 'net: in Device Manager > USB Controllers, right click on the USB Root Hub entries and run scan for hardware changes. The second one tried brought the PS Audio Directstream's entries back to life. Probably a safer way now that I know this would be to uninstall the driver before the major updates.
     
    highstream, Jan 22, 2017
    #5
  6. sygnus21 Win User
    Well you still haven't said what DAC it is, but with my DAC I've never have any issues with any Windows 10 updates whatsoever. And I've got all the latest updates. Current Windows version is 1607 (build 14393.693).

    Anyway glad to see you solved it.

    Peace *Cool

    Oh, and can you mark this as solved so we don't waste time typing in suggestions when the issue is actually solved. Thanks, would be a courtesy to others.
     
    sygnus21, Jan 22, 2017
    #6
  7. It's in my last post, next to last line.
     
    highstream, Apr 5, 2018
    #7
Thema:

Dac not seen after Win 10 system image rollback (1607 fail to 1511)

Loading...
  1. Dac not seen after Win 10 system image rollback (1607 fail to 1511) - Similar Threads - Dac system image

  2. Can't rollback to win 10

    in Windows 10 Software and Apps
    Can't rollback to win 10: I have windows.old folder in my c drive but I can roll back into windows 10 and it has only been 3 days btw i installed win 11 by changing in apriserieses.dll https://answers.microsoft.com/en-us/windows/forum/all/cant-rollback-to-win-10/df2a258e-2ccc-4fd0-848b-62ab597f614f
  3. Windows 10 Rollback Upgrading From 1607 to 1803

    in Windows 10 Installation and Upgrade
    Windows 10 Rollback Upgrading From 1607 to 1803: Getting the following error after running the Windows 10 1803 upgrade on a PC currently loaded with 1607. Error: SetupDiag reports rollback failure found. Failure Data: Last Phase = SafeOS,Start Last Operation = Save SAM and SECURITY hives Error = 0x80070005-0x2000D...
  4. Upgrade fails for win 10 1511 --- load from usb ?

    in Windows 10 Updates and Activation
    Upgrade fails for win 10 1511 --- load from usb ?: I have 1511 installed and hit the issue with a couple of updates not installing so I can't install the Anniversary and follow-on upgrades. Has anyone used the Media creation tool, downloaded the Win 10 Home/Pro x64 v.1607 to a USB stick, and then performed an in-place...
  5. WIN10 upgrade 1511 to 1607 fails. Error 0dx000009a

    in Windows 10 Updates and Activation
    WIN10 upgrade 1511 to 1607 fails. Error 0dx000009a: I have installed WIN10 (ver. 1511) a couple of months ago. While trying to solve a driver issue I've been advised (by MICROSOFT) to upgrade to ver.1607. Several upgrade attempts all failed (with code 0xd000009a) What does it mean? Any more details needed? How can I resolve...
  6. Updated Version 1511 to anniversary update, 1607, but still at 1511

    in Windows 10 Updates and Activation
    Updated Version 1511 to anniversary update, 1607, but still at 1511: Hello all. Running windows 10 pro 64 bit. I've updated from Version 1511 to the anniversary update, 1607. Or at least, I thought I did. The update went well, no hiccups, no errors. Used windows update, let it downloaded and install and rebooted. Alas, system...
  7. WIN 10 November Update - Black Screen Fail and Rollback

    in Windows 10 Updates and Activation
    WIN 10 November Update - Black Screen Fail and Rollback: After pulling my hair out over the latest update, not, well, updating, I turn to the experts *Smile WU downloads fine, and when I duly start the process, it all looks to install okay, until it gets to the black screen - pretty much all files copy over, but then usually at...
  8. Win 10 1511 "upgrade" with base image in audit mode?

    in Windows 10 Installation and Upgrade
    Win 10 1511 "upgrade" with base image in audit mode?: So I have a base Win 10 image we deploy using SCCM to new systems. This was a clean install setup as a base using Microsoft's suggested practice of customizing using Audit Mode. I've been using this successfully (using Windows PS ISE to do Windows updates to the base image in...
  9. Update from 1511 to 1607 failing

    in Windows 10 Installation and Upgrade
    Update from 1511 to 1607 failing: Win 10 Pro i7 desktop (upgraded from 8.1), 1511 working fine. Tried four times this week to go from 1511 to 1607 and failed four times. Well, actually the first time via USB setup it succeeded, but when a day later I needed to boot into Safe Mode, startup ran on and on (four...
  10. Downgrading from Win-10 1607 to Win-10 1511

    in Windows 10 Installation and Upgrade
    Downgrading from Win-10 1607 to Win-10 1511: Recently Windows 10 on my desktop PC upgraded itself to Build 1607. Immediately my Brother printer stopped working (it was removed from the list of printers and could not be reinstated). Other funny things happened too. I downgraded back to Build 1511 and the printer now...