Advertisements
Windows
-
-
January 24, 2013There are a few different methods to try when it comes to repairing a corrupt WMI (Windows Management Interface) 1. Open Up a Command Prompt If running Windows Vista or Windows 7 you need to Run The Command Prompt As Administrator. Right click the Command Prompt and then click Run as administrator. 2. Type this command and press Enter net stop winmgmt 3. Using Windows Explorer rename the folder C:WindowsSystem32WbemRepository to C:WindowsSystem32WbemRepository.old 4. Type this command and press Enter net start winmgmt 5. Restart the computer The second method to try is 1. Open Up a Command Prompt If running Windows Vista or Windows 7 you need to Run The Command Prompt As Administrator. Right click the Command Prompt and then click Run as administrator. 2. Type this command and press Enter rundll32 wbemupgd, UpgradeRepository This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log C:Windowssystem32wbemlogssetup.log 3. Restart the computer The second method to try is 1. Type this command and press Enter winmgmt /salvagerepository 2. Restart the computer
-
January 22, 2013This works on Vista and Windows 7. To install .Net 1.1 and SP1 into Vista or Win7 (32 or 64 bit). Create a new folder named DotNet in C: drive (C:DotNet is used in this guide, you can change to any folder you prefer, but ensure that you use correct path in the following steps). Download Microsoft .NET Framework 1.1 Redistributable Package(dotnetfx.exe ). Make sure the setup file is saved as dotnetfx.exe . Download Microsoft .NET Framework 1.1 Service Pack 1 (NDP1.1sp1-KB867460-X86.exe ). Make sure that the file is renamed and saved asdotnetfxsp1.exe , so that the rest of the steps can be followed easily. Move both installation files into the same directory (i.e. C:DotNet), if you’re not saving them together. Open command prompt as Administrator . Change to the directory where the two installation setup files for .NET 1.1 are saved (i.e. C:DotNet). Run the following commands one by one, press Enter after each one. dotnetfx.exe /c:”msiexec.exe /a netfx.msi TARGETDIR=C:DotNet” Then click on “Yes” when prompted to answer “would you like to install Microsoft .NET Framework 1.1. Package?” dotnetfxsp1.exe /Xp:C:DotNetnetfxsp.msp msiexec.exe /a c:DotNetnetfx.msi /p c:DotNetnetfxsp.msp Install Microsoft .Net Framework 1.1 with slipstreamed/integrated Service Pack 1 by running netfx.msi created in the working folder.
-
October 1, 2012A new vulnerability in Java has been discovered. The vulnerability allows an attacker to gain control of a victim’s computer. The researchers have confirmed that Java SE 5 – Update 22 (Java SE 5 build 1.5.0_22-b03) Java SE 6 – Update 35 (Java SE 6 build 1.6.0_35-b10 ) Java SE 7 Update 7 (Java SE 7 build 1.7.0_07-b10) This vulnerability is caused by a discrepancy with how the Java virtual machine handles defined data types and in doing so violates a fundamental security constraint in the Java runtime, allowing a complete bypass of the Java sandbox. The flaw allows the attacker to gain complete control of a victim’s machine through a malicious website. Affected web browsers are Safari 5.1.7 Opera 12.02 Chrome 21.0.1180.89 Firefox 15.0.1 Internet Explorer 9.0.8112.16421 Even with fully patched Windows 7 32-bit operating systems you are susceptible to the attack. So far there are no reports of the flaw being used in any malware. I would take a few preventative steps Reducing the number of active runtimes (code execution environments) on your system If you do not need Java uninstalling or disable it Oracle released a fix for the most critical vulnerabilities on August 30. The last exploit would allow an attacker to use a malicious Java applet to install programs, or read and change data on the system with the privileges of the current user. But now another flaw in that fix allows a hacker to bypass the patch. That bug in Oracle’s patch still hasn’t been patched, leaving users vulnerable to both the new flaw and the previous attack. It’s not yet known when or if Oracle will fix this issue. Oracle has been provided with a technical overview of the bug and example code outlining the flaw but has not yet acted upon it.
-
August 21, 20121. Downloading latest drivers (v14.19.50) for XP from the manufactures site and extracting them to a separate folder 2. Booting Windows 7 or Vista in the safe mode 4. Then navigate to Device Manager -> Video Adapter (VGA compatible) -> Properties 5. Click Driver -> Update driver -> Browse -> Let me pick -> Display adapters -> Have disk -> give path to the folder of the extracted driver 6. After you get error about driver installation in Device Manager click on “Scan for new hardware” 7. Boot your W7 or Vista in “Disable driver signing enforcement” mode
-
Microsoft released a forth quarter security report stating that the worm Conficker is still infecting 1.7 million computers and work stations. This news comes more than three years after the worm was first detected. The rate of infection has increased despite widespread availability of tools to fight it. Conficker has many different versions which make it hard to fight on large scale networks. Although Microsoft had patches out way before a lot of companies were not patched. Conficker can also turn off Automatic updates and BITS (Background Intelligent Transfer Service). Despite Microsoft’s security patches and updates for Windows XP and Vista companies and end-users are still vulnerable due to Conficker’s ability to self-update by automatically connecting to hundreds of attacker-controlled domains. Microsoft recommends two things 1. Adopting Better AV (Anti-Virus Solutions) and Malware Protection 2. Strong and Better passwords
-
June 10, 20121.Open the IIS manager console 2. Click on the server name 3. Click Server Certificates 4. Right Click and select Create Domain Certificate 5. Complete all the needed information and select your certificate store server. Make sure you use the FQDN for the server in the Common Name section. 6. Right Click on Default Web Site 7. Click edit Bindings 8. click on edit for https then select your newly issued certificate 9. You do not need to reboot the server or restart IIS.
-
Fix: Could not start the Automatic Updates service on Local Computer. Error 0×80004015: The class is configured to run as a security id different from the caller Issue: Automatic Updates (AU) service will not start attempting to start the service manually results in the following error on a Windows XP SP3 machine: Could not start the Automatic Updates service on Local Computer. Error 0×80004015: The class is configured to run as a security id different from the caller Solution From a command prompt re-register the Automatic Updates dll by running: regsvr32 /u wuaueng.dll regsvr32 wuaueng.dll Change the Automatic Updates service startup from to Automatic if this is not done already. The Automatic Updates service should now start on its own on reboot. Make sure Background Intelligent Transfer Service (BITS) and Windows Management Instrumentation (WMI) are both set to Automatic as well before reboot. Sometimes if this happens as a result of a virus you will need to adjust those settings.
-
May 10, 2012
Using Task Scheduler to schedule the computer to shut down and restart at a specific time
Click Start, Run and type control schedtasks Double-click Add Scheduled Task. The Scheduled Task Wizard starts. Click Next. Under Click the program you want Windows to run, click Browse. In the Select Program to Schedule dialog box, locate the %SystemRoot%System32 folder, locate and click the Shutdown.exe file, and then click Open. Under Perform this task, specify a name for the task and how frequently you want this task to run, and then click Next. Under Select the time and day you want this task to start, specify a start time and date for the task, and then click Next. Type the user name and password to run this task under, and then click Next. Click to select the Open advanced properties for this task when I click Finish check box, and then click Finish. Click the Task tab. In the Run box, specify any additional parameters that you want to use with Shutdown.exe. Click OK. Important: In the 10th step, you need to add the parameters for the Shutdown.exe command. To immediately shutdown the system (0 second timeout), the command-line would be: shutdown.exe -s -t 00 To reboot the system immediately, this command: shutdown.exe -r -t 00 For additional help, type Shutdown /? at the Command Prompt. Scheduling the Shutdown.exe without any parameters will not help. It will just execute with a exit code 0 (success) -
April 3, 2012There is a few ways this can be done on Windows 7 and Vista using this great tool Windows 7 & Windows Vista I found this great tool works great http://www.thewindowsclub.com/downloads/Fix%20WU.zip In windows xp I found the Microsoft way worked the best of reinstalling the Windows Update Agent http://support.microsoft.com/kb/943144