Possible to Manually install WLAN services on Server 2012?


Recommended Posts

I have 2012 setup in my lab at home, and wanted to try link aggregation using two NICs using a program called Connectify Dispatch, which requires WLAN services to be installed. I tried to install WLAN services, but after a reboot, it always says "Failed to update Windows updates, rolling back changes" or something to that effect. I have tried a "clean boot" (disabling services and start up items) as well as trying to install in safe mode, but can't get it to work. As a test, I re-installed 2012 in a Hyper-V VM and was able to install WLAN services there. I've checked for file corruption by running SFC /SCANNOW, chkdsk, and making sure windows updates were up-to-date.

Short of running something like process explorer and watching what gets changed when installing the WLAN features, is there an easier way to copy needed bits from the VM to the host, or would it be easier to just re-install the OS? Technet forums show nothing else besides clean installs or safemode/clean boot installs, so I'm out of options besides trying to manually copy files across, or to possibly try linking the host with the VM in server manager and installing that way, although i don't know if it gets the feature bits from the box it's installing on or the machine doing the installing.

I'm not totally against a re-install, since all apps are in Hyper-V Vm's on a RAID array, so it would not be too difficult to do a re-install.

  • 5 weeks later...

You may be stuck with a reinstall. I think you have some slight corruption in your side by side assembly database, and SFC cannot fix these issues. Your other option is to report the issue to Microsoft, and hope they release a "System Update Readiness Tool" for Server 2012 that can correct these problems.

 

I have the same issue on a Hyper-V/RemoteFX test server and have not found any other way to resolve the issue except to reinstall. I cannot add or remove roles, or install some of this month?s Windows Updates.  Since it?s only a few days until the Server 2012 R2 beta comes out, and this is my personal desktop and not a production server, I'm just waiting for that.

 

 

The only other way you can fix the problem is to figure out exactly where the corruption is within the SXS folder and replace those items from another server.  This can be difficult if the SFC tool doesn't report what descriptor is corrupt.

Hey, The System Update Readiness Tool functionality is built into DISM in Windows 8/2012! This may very well fix your problem.

DISM /Online /Cleanup-Image /RestoreHealth

http://blogs.technet.com/b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx
 

I have 2012 setup in my lab at home, and wanted to try link aggregation using two NICs using a program called Connectify Dispatch, which requires WLAN services to be installed. I tried to install WLAN services, but after a reboot, it always says "Failed to update Windows updates, rolling back changes" or something to that effect. I have tried a "clean boot" (disabling services and start up items) as well as trying to install in safe mode, but can't get it to work. As a test, I re-installed 2012 in a Hyper-V VM and was able to install WLAN services there. I've checked for file corruption by running SFC /SCANNOW, chkdsk, and making sure windows updates were up-to-date.

Short of running something like process explorer and watching what gets changed when installing the WLAN features, is there an easier way to copy needed bits from the VM to the host, or would it be easier to just re-install the OS? Technet forums show nothing else besides clean installs or safemode/clean boot installs, so I'm out of options besides trying to manually copy files across, or to possibly try linking the host with the VM in server manager and installing that way, although i don't know if it gets the feature bits from the box it's installing on or the machine doing the installing.

I'm not totally against a re-install, since all apps are in Hyper-V Vm's on a RAID array, so it would not be too difficult to do a re-install.

Just a heads-up - you CAN team disssimilar adapters in either Windows 8 or Server 2012 - at one point I teamed a gigabit and a wireless (G in this case) adapter.

 

While similar-bandwidth teaming is preferred (as is the case with any teaming solution), Windows Server 2012 was the first non-Linux/UNIX/BSD server OS I'd any experience with to allow wired/wireless teams.

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

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!