Jody Thornton

I have posted this question on the Windows 8 Forums as well. So a bit of an involved situation here: First off I wanted to add a registry key to make Windows Defender scan for incoming files only. I was going to add this DWORD value to HKLM\Software\Microsoft\Windows Defender\Real-Time Protection: RealTimeScanDirection = 1 However I couldn't because the permissions likely didn't allow for it. So I changed the owner of the "Real-Time Protection" key from SYSTEM to Administrators (I even tried for my user account which is just the renamed Administrator account). I assigned full control rights to Administrators and "Me". However I still cannot add the DWORD value. Now I made myself owner of the entire Windows Defender key thread, and I can change values of other keys. But I can't add or change anything in the Real-Time Protection key. I'm perplexed. After that, I want to see if there's a way to reset the permissions on the Windows Defender keys (the entire tree).. Any takers?

I'll be delighted if that, too, turns out to be the case -- one look over to the left, below my MSFN join date, will confirm it! --JorgeA Ah I see! Cool!

Now there is no malware on that DeviantArt link, is there?

Yeppers, I am quite aware of all of that. But thank you. I just didn't want you to think that was lost on me, especially since I had already considered a similar situation with Server 2008 "classic" and Vista, and also with Server 2003 and XP x64. In the latter case, many updates were able to be used directly.

I think what'll do is try this after creating a restore point. I can always undo it after that. Additionally, I will boot up into a Linux live CD and create a backup of Windows system folders (while they're not in a locked or in use state, and that way I can just move it back if I need to.) I'll keep you posted with what I find out. I was hoping that a similar development arises for Vista after April 2017, using Server 2008 updates. Again, we'll see.

I'd like to try Windows XP with the inexperience pack that allows a complete Windows 2000 appearance (right down to the actual icons)

Gotcha. ComputerNerd; feel free to chime in. But thank you JorgeA.

I don't know if it's been all that much of a risk to run for the last six months. I'm at work right now on Firefox v43 running on Windows XP SP3 (nowhere near as stable and secure as Windows Server 2003 or Windows XP x64 Edition.) We've had NO PROBLEMS with this machine in the last couple of years, and keep in mind I was one of those who was VERY concerned about security post-extended support.

Yes it was a GX110.

Yeah I remember using a Dell Optiplex Pentium III desktop with a maximum of 512 MB of RAM that was addressable.. Now I never tried putting two 512 PC133 DIMMs in it, so I just had two 256 MB DIMMs. It worked well with Windows 2000 I will say.

ComputerNerd and JorgeA. I just wanted to bump this to get an answer. It sounds as if you knew for a fact this was presently workable.

So we know for certain that Server 2012 updates DO WORK on Windows 8, even as of now? Or is that speculation? I'm at work right now, so I am unable to try ... lol

Happy New Year Noel Now if Microsoft were to abandon the Explorer shell, and go completely with a Metro/Modern model (which I think is the long-term plan) then in time, would you not just move your development focus to modern apps, and provide extended support for desktop apps? I'm simply asking that if Microsoft were to go all Metro, would the demand for you to develop new conventional applications not also decline in the medium-long term?

Happy New Year and Happy Forthcoming 15th MSFN Anniversary

Not only that, surprisingly (if you believe all the MS FUD) the sky has not fallen on our heads (yet ). jaclaz I'm at work using an XP box right now, so that is a testament to what you're saying. Oddly enough, I'm sure we could do most of my job on a Windows 2000 machine. We'd have to use Firefox 17, but that is still compatible enough I'd think.

Hard to believe that for XP itself, that EOL was almost two years ago. Time flies eh?

I'm like that about a lot of stuff. I have a basic migration path for Windows that I plan to follow until 2023 (when I'll be 53 ... lol) A lot of forum posters say, "Why plan that far ahead?" I don't know what I'm doing tomorrow". And it's likewise for me, but I still like to at least have a road map. Sure, it may go out of date, but at least I have a basic plan in place. I really worry about the possibility that Microsoft will cripple or disable features on old operating systems or even revoke licenses of old OS releases. In the latter case, should such a thing ever happen, I would entertain becoming part of a class action lawsuit to receive back monies paid for such products. Good talking to you Noel.

Just a curiosity. Hard to pin down info on it. Will Windows Defender Updates continue to be available for Windows 8 users? Also, being inspired by the POSReady hack, has anyone ported updates and patches from Server 2012 to Windows 8?

On another thread, you were hinting at being unsure whether this was a good long term strategy. What started giving you doubts? Sounds like you're churning along fine. On Windows 8.0, I'll be frozen in time involuntarily. I wonder if Defender updates will stop.

OK this is strange. I got my own task working (without the script). What changed it? I called my original task "Windows Defender Update". I changed the name to "Windows Defender Update Task". Now it works. Huh???

Hmmm I run the script at a command prompt. It works. I load it into a task. I run the task and it takes forever. Windows Defender does not update and the task is deleted. Go figure.

I think we're in business - you are the man!

Correct, but you are able to schedule updates using the Task Scheduler if you prefer to manually update Windows. It's no different than if I were to update Windows Defender using the Update tab.

I attempted exporting my scheduled scan task to XML, and then importing it as a new task. Step by step, I make changes to several parts of the task (the time to run, the name and the description). Each time I make a change, I save the task and run it (at this point, a full scan task). Then I change the parameters to -SignatureUpdate, which runs a definitions update. The task deletes when I run it.

In the Windows 8 Task Scheduler, I have set up a scheduled nightly task to update Windows Defender. I turn off auto updates. Instead, I have Windows download the updates, but let me decide when to install them. So after, making the scheduled task, I attempt to run it manually (just to test it). Every time I do so, no updates occurs, and the task deletes itself. I attempt to recreate it, but the same result repeats itself. Any reason why it would delete itself? I've compared it to the "Scan" task, and all of the triggers and options are the same. The time to run, and the command parameters are the only things that are different.