Well it requires a couple reboots which isn't an improvement because it messes with trusted store I think? I want it to be improvement but I don't think it is? We need WPA key delete inside windows so if you can stop the service that prevents WPA key delete inside windows then you improved IR5
1. Yes, I know he did. I wanted to make one 2. Yes, I remember that also. I had made a little batch file, but it was really bad. 3. I didn't know that you had to have at least 1 rearm left. The other thread said that it sets it back to default. I'll have to edit the title also But now, my final question for Josh: Even though I don't have the auto detect yet, does it work otherwise?
And yes, someone really needs to know how to do that. That would be so much better than all the methods out there. If one of you figures that out, I need to know
If one we're to read the thread again it was not seen as viable solution since it's dependent on always installing at W7 install when rearms are full hence it's dependent on a certain status moment in linear time 1. So it can't be used if one has no rearms! 2. How and when would it determine to restore 3. I think this method requires reboots so it isn't more convenient 4. Messes with trusted store which I think requires reboot's 5. I think PMR's title was incorrect and should be restore not reset...lol So as I've said hundred times we need to delete WPA key inside windows then we have improvement over the current standardized rearm concept IR5 Edit: I'm pretty sure HAL7600 deletes WPA key inside windows but it is still secret
Yeah, it's not as efficient as it could be. I am starting to realize where this is going. Do you know what WPA key you are talking about? Because if so, I want to snoop around. There is the method used in IR5, but those registry values can only be accessed by repairing the computer. If there is some way to access those registry values without a reboot, this could get better. Is it possible to use programs such as Unlocker on registry values? If so, that could lead us somewhere.
Well I mentioned that HAL is doing it without visit to RE/PE so that is biggest clue Too bad since those solutions are not working for all regarding SP1 Here is the registry stuff in RE/PE Code: reg load HKLM\MY_SYSTEM "%~dp0Windows\System32\config\system" reg delete HKLM\MY_SYSTEM\WPA /f reg unload HKLM\MY_SYSTEM Then default key install is required And you got use the IR5 anti-nag reg setting Anyone try deleting the WPA key with unlocker ...lol I think sec9tos HAL method doesn't requires default key install based on time HAL takes to install and the fact that watermark doesn't appear when installing HAL requires simple reboot Not sure when he deletes WPA?
Alright. And I've seen those registry keys before. I had to do the MPC because I was unaware that my drive letter changes in RE. Maybe you could ask the creator of HAL for the source code that deletes those values without RE. I have to go right now, I'll be back in about 30 minutes. I want a lot of posts about how this new reset method is going to work. I know you can figure it out timesurfer
This is an private development project, consists on run SLUI and clear from memory offsets with "R" arguments, generating a fatal error on slui, unlocking the registry for WPA Delete inside Windows... @SS111 W7 Ultimate x86 with 1 rearm: Fatal error and System.IO.Error
Well I'll develop and test it mad but I have no idea how to make service accomidate WPA delete inside windows and not sure if key install is necessary inside windows WPA delete And yea I already asked him for help with IR5 and he declined for appropriate reasons relating to HAL development Well let's break it down for me: A. Inside windows method (PMR) B. Outside windows method (IR5) Let's go from there cause I'm getting confused And yea I don't remember PMR resetting just restoring cause the conversation in his thread suggested it had inconsistant results. I think this is where confusion if his restore/rearm method lives? I'm not sure what is does so they would have to freeze the current status correct? Also I think I remember seeing some code in TTG that implied that default key was used/installed in XML file so that might be hint about your question? IR5 get's to RE fine as far as I've seen Basically inside windows method is ideal as have I said for almost 1.5 yrs...lol
No, the changes is only in the memory, after reboot the activation system become's normally, after this, slui get a fatal error, crashing the Registry Kernel Permissions, deleting sucessful the WPA key, Restarting slui after WPA patch, the activation system "feel nothing" ...