I did however install the KB971033 now I am flagged as not genuine windows copy, If I system restore back to the time I installed the update my computer doesnt get the messege but if I restart it does HELP ME!
Windows 7 Loader V1.9.7 X86 X64
I only have a version of windows because the one I own is 64 bit but as we all know, there are 9999 bugs with 64 bit so I have a version for 32 bit, but damn windows reenabled updates. I never have them to automatically, and it keeps on changing it to automatically every month or so.
Why is it that after i used a loader, it shows that windows is activated, and it shows the product-id. Thats good i know..But..Should i remove the WAT so the product-id etc. will disappear?
Works perfectly. Somehow I inadvertently installed this update. I ran a few of the above commands, got rid of the update that caused my copy to become invalid, rebooted and my copy of windows 7 is activated again, microsoft security tools now work again, after it initially say this version of windows is not activated. Pressed one of the buttons to recheck and it resolved everything, now my windows is re activated, can get updates again and windows is no longer reporting that is not activated and its not geninue. Did not need to apply any patch or anything!Just follow the instructions because they work like a charm!
Hey, just wanted to say thank you, this worked, I ended up uninstalling the SP1, but my stuff was all messed up still, after a few hours of looking at your site, and trying a few methods, i finally used windows loader and the genuine check online, thank you.
hey guys! i fixed my sp1 non genuine by system restore back to time before i installed the sp1 then u can see the 971033 after u install sp1 it hides 971033 inside i guess. So it took like 2 hours i guess first it startup in windows all screen black only mouse then i restart again and then ok. I looked the 971033 uninstalled and after hide the sp1 too.
Do not install kb971961 it is the newest and latest attempt from micrshaft to disable cracked versions of windows 7 x64, I simply uninstalled it and everything is working fine, it is labeled as Important
removewat works after the fucking watermark at the bottom of my desktop.. now i can update my windows without knowing if i am genuine or not because i cannot see the genuine logo at system properties :)..
I just wanted to say thanks! I was able to fix it by doing the rearm windows instructions. I have Windows 7 Ultimate and had tried everything else! I did uninstall the update first and then hid it from updating later. After that I ran the rearm commands and was happy to see that the messages were not there anymore. THANKS AGAIN!
If you want to keep Windows update from ever installing it, just to into services, and disable the Windows Update service, and turn off all Windows updates. That will solve the problem. I never use Windows update. With good firewall and antivirus sofware, windows update is just redundant, and not needed, so I just disabled it in Services, and be done with it.
This method still works!!!*Uninstall KB971033.*Restart the computer.*Install latest windows 7 loader.(Just google it)*Run loader & restart when prompted.*Go to windows site & validate windows.*Welcome to Windows! GOOD LUCK!!!
1 uninstall kb971033 u can find it in the list of installed updates2 install latest windows loader, run and reboot when it tells u3 go to start and run the command line interface in administrative mode by typing run in the search box and instead of just pressing enter press ctrl + shift and enter, the command line interface should pop up in administrative mode4 paste the rearm command wich is : slmgr.vbs -rearm and enter and reboot when it tells u to5 windows genuine ? and no msg6 yeah fu windows activations technology WAT
kept getting the windows not genuine message til i went out of my gourd finally today.unearthed this page and tried the icacls %WINDIR%\\System32\\sppcomapi.dll /deny *S-1-1-0:Fworks like a ^*%*%$ charm. kudos.
Thanks! I was having a problem with window popping up saying windows not genuine, I called microsoft and they were no help, I uninstalled this update (kb971033) as said here and my pc is working fine without that darn window popping up.
1 uninstall kb971033 u can find it in the list of installed updates2 install latest windows loader, run and reboot when it tells u3 go to start and run the command line interface in administrative mode by typing run in the search box and instead of just pressing enter press ctrl + shift and enter, the command line interface should pop up in administrative mode4 paste the rearm command wich is : slmgr.vbs -rearm and enter and reboot when it tells u to5 windows genuine and no msg6 yeah fu windows activations technology WAT
It is distinct from the "MBR boot code" method that was used by legacy BIOS systems. See Arch boot process for their differences and the boot process using UEFI. To set up UEFI boot loaders, see Arch boot process#Boot loader.
UEFI defines variables through which an operating system can interact with the firmware. UEFI boot variables are used by the boot loader and used by the OS only for early system start-up. UEFI runtime variables allow an OS to manage certain settings of the firmware like the UEFI boot manager or managing the keys for UEFI Secure Boot protocol etc. You can get the list using:
The UEFI Shell is a shell/terminal for the firmware which allows launching EFI applications which include UEFI bootloaders. Apart from that, the shell can also be used to obtain various other information about the system or the firmware like memory map (memmap), modifying boot manager variables (bcfg), running partitioning programs (diskpart), loading UEFI drivers, editing text files (edit), hexedit etc.
DUET was a TianoCore project that enabled chainloading a full UEFI environment from a BIOS system, in a way similar to BIOS OS booting. This method is being discussed extensively in -linux-and-windows-uefi-boot-using-tianocore-duet-firmware/. Pre-build DUET images can be downloaded from one of the repos at _uefi_duet_builds/tianocore_uefi_duet_installer. Specific instructions for setting up DUET is available at _uefi_duet_builds/tianocore_uefi_duet_installer/blob/master/Migle_BootDuet_INSTALL.txt . However, as of November 2018, the DUET code has been removed from TianoCore git repository.
In RHEL 8, the kernel command-line parameters for systems using the GRUB2 bootloader were defined in the kernelopts environment variable. The variable was stored in the /boot/grub2/grubenv file for each kernel boot entry. However, storing the kernel command-line parameters using kernelopts was not robust. Therefore, with a future major update of RHEL, kernelopts will be removed and the kernel command-line parameters will be stored in the Boot Loader Specification (BLS) snippet instead.
This issue was part of the build process script I was using and it does a npm clean and install everytime with a bunch of other things .So this issue appears many times in the same machine where we automated tests using phantomjs. I got some time to look into this issue and it seems my corporate proxy is blocking the download from -2.1.1-windows.zip. I knew this before and had manually installed phantomjs binary and added to system path but the npm install still trying to download locally as showing in the log below.
The work around I used was to get the phantomjs-2.1.1-windows.zip and copy it to the C:\Users\\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip and that resolved the issue with the build script.If someone cleans the temp directory,issue will come back. Even this is a work around but the corporate proxy cannot be unblocked for obvious reasons :) 2ff7e9595c
Comments