Windows 7 Home Premium hanging on shutdown


Recommended Posts

I installed my 64bit audiophile 2496 drivers in Windows 7 Home Premium. After pressing shut down or restart, all my applications are closed but it hangs on the shut down screen.

With some research I found the solution as stated below...

M-Audio audiophile Delta 249 conflict Joepsz, a poster to Microsoft?s TechNet forums, has discovered a fix that involves stopping the ?Audiosrv? and ?AudioEndpointBuilder? processes associated with the M-Audio audiophile Delta 249, which exhibits a conflict with Windows 7. The fix is as follows:

1. Create a .bat file (create txt file and change extention to .bat)

2. Right Click on file > ?edit? and enter following info:

* net stop ?Audiosrv?

* net stop ?AudioEndpointBuilder?

3. Save file as ?Audio stop?(or whatever you want) to your main drive ie: C:\Audio stop

4. Open ?run? from start menu and enter ?gpedit.msc? (without quotes) and hit ?OK?

5. Now navigate from right pain of window ?User Configuration? > ?Windows Settings? > ?scripts (Logon/Logoff)? > ?Logoff?

6. From window that opens from clicking ?Logoff? Click ?Add? then browse to where you saved ?Audio Stop.bat? earlier and double click on it.

7. Hit ?Apply? and close.

The problem is that Home Premium version doesn't have the Group Policy Editor (gpedit.msc) program, and there doesn't appear to be any other way to create a logon or logoff script.

Does anyone know a way around this?

Thanks

yxz, I tried to run that command but unfortunately it didn't work.

I also tried editing the registry by following what this site says

Note that implies midification of the Registry, it is recommended to make backup before proceeding

Open notepad and copy the code below:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts\Shutdown]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts\Startup]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts\Startup\0]

"GPO-ID"="LocalGPO"

"SOM-ID"="Local"

"FileSysPath"="C:\\Windows\\System32\\GroupPolicy\\Machine"

"DisplayName"="Strat?gie de groupe locale"

"GPOName"="Strat?gie de groupe locale"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts\Shutdown\0]

"GPO-ID"="LocalGPO"

"SOM-ID"="Local"

"FileSysPath"="C:\\Windows\\System32\\GroupPolicy\\Machine"

"DisplayName"="Strat?gie de groupe locale"

"GPOName"="Strat?gie de groupe locale"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts\Startup\0\0]

"Script"="C:\\script1.bat"

"Parameters"=""

"ExecTime"=hex(b):00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

but it didn't work either

http://www.m-audio.com/index.php?do=suppor...serie_ID=1#tabs

as you figured out windows 7 is hanging on the driver and they do not seem to have a windows 7 driver yet

you could

try the vista sp2 driver

sign up for their beta driver and see if that works

unistall and wait for a win 7 driver

or try what you suggested

good luck!

this should work

schtasks.exe /create /tn killaudio /sc onevent /ec System /mo "*[system[Provider[@Name=Microsoft-Windows-Winlogon] and EventID=7002]]" /tr c:\killaudio.bat /np /rl highest

I tried to run that command in an elevated cmd window and changed the appropiate path and file name, but it didn't work.

SfIsHeR1701, theses windows 7 drivers are in beta and I think they are already aware of this, its the top post in the beta drivers forum

the scheduled task works here (runs the .bat at user logoff)

what exactly doesnt work?

does the "fix" even work?

I've tried thre fix manually by using the net stop command on the service to stop it, and it works fine, windows shuts down without hanging.

I just need a way to have the batch file triggered on shut down only, and not on user logoff or switching. I hope that clarifies things

yxz,

I also tried that method and it does not work. But thank you for continuing to offer solutions. I think task scheduler is the key to solving this, I just don't know how to get it to run prior to shut down.

mduren2445,

I tried the vista sp2 driver and that also causes the same hanging at shut down.

Is there any way to get the Group Policy Editor onto the Home Premium version?

  • 4 weeks later...

Hi there - I've got the EXACT same problem with my Tascam US-122 soundcard. I'm also using 7 Home Premium.

The only simple way round that I figured out is to just unplug the USB connection to the soundcard prior to shutting down. When I do this, the comp shuts down no problem. Leave it in, it hangs. Obv if you've for an internal soundcard that's not so easy....

Haven't found another solution as yet.....

Just thought that might be helpful - you are not alone!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!