Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ralmada

Pages: [1]
I mean that i would like to run your wmi repair tool (or its commands) directly by the command prompt instead of interact with his interface (or without having to press start button). I use Lansweeper for general information/management and PAExec when i can't access some computers remotely without interrupt local users's routines (sometimes the multiple RDP connections do not work properly and nor always i can spend time analyzing and fixing this in that moment). If possible, of course. :shy:

No way dude, i've tried your suggestion and the commands from this tool: but not worked too. The only working successful method is still your wmi repair tool, but i can't run it in silent mode. :(

Many thanks, Tom! I'll test it soon. And regarding to topic, updating it (as we spoke via PM):

"Hey Tom, about the topic []: sorry for not keep you updated. I realized that i've caused the issue by disabling that virtual driver. Then when i told that the problem persisted even re-enabling that driver, i found that it only stops ocurring when literaly removing (whithout need to mark "exclude" option) and reinstalling the network card's driver. Some tests you suggested me, i could not do them because of administrative privileges that i have not. So basically, i've caused an issue and i'm fixing it manualy only when the gpo that reverts my mistake fails applying someway. Everything is working fine now, so thanks a lot for all interactions. Can you give me another information? I'm using that separated wmi repair tool to refresh some messed old Windows installations in relation to antivirus status. Is there some command line to run the repair.exe in silent mode bypassing the start button? I'm asking because i use paexec to make some maintenance routines remotelly without interrupt users's routine. Many thanks again."

I also did it but nothing changed. I found that batch in a Russian forum but I still can't confirm if it is the same content (I will check at my work soon), here the parameters:

echo off
echo Restart "Network Location Awareness" service
net stop "Network List Service"
ping localhost -n 5 > nul
net stop "Network Location Awareness"
ping localhost -n 5 > nul
net start "Network Location Awareness"
ping localhost -n 5 > nul
net start "Network List Service"
echo configuring "SharedAccess" service
sc config SharedAccess start= DEMAND
shutdown -r -t 1
del %0

It's the icon that indicates that there are available wireless networks when you are not connected to none ("the little yellow sun" attatched).

I've discarded Aruba environment, there's nothing wrong. I was checking with the admin since problem begins.

The rest of checklist i had already did.

One more interesting troubleshooting that i will check soon (this is exactly my problem):

The first batch file is no more available but i will track that commands.

Thanks a lot for your interest helping me.

I already have that and some more parameters in a batch file for troubleshooting, i just didn't checked if it's necessary to remove and reinstall wireless card driver or not after these commands. Also i have to find another solution for that damn wrong icon without disabling that virtual wifi driver.  :confused:

Now, it seems sometimes I have to choose the less worse option between wireless limited access and wrong connection icon (obviously the second one). If I solve first issue, the second happens and vice-versa. Lol
I'm still trying to understand the entire context.

After many days looking for the source of my problem, i've finally found it! Someway that i can't understand yet, after disabling "virtual wifi filter driver" (under device manager -> show hidden devices -> non-plug and play drivers) and restarting Windows - or deactivating/reactivating the wireless card - the problem begins. I have disabled that virtual wifi driver as a troubleshooting that i saw on internet for other network problems that i've faced here (

Hello all! Here in my job all workstations are over a domain and the entire wireless structure is supported by a lot of HP/Aruba access points, all of them controlled by AirWave manager.
Then, the problem that is occurring with certain frequency is that some Windows's wlan autoconfig and related services are delaying too much to start, and this is preventing domain users to logon on the machines, because here there is no cache logon (disabled by gpo), so when Windows's wlan structure presents any missfunction, the connection appears partially made and keep in a "limited access" state until all Windows's wlan related services finish to start completely, so the workstation can be finally authenticated on the domain and users can make a successful logon.
So searching some forums i've found some troubleshooting that i still can't test, that involves file's proprietary and file's permission changes:

Many thanks in advance!

Pages: [1]