1 reply to this topic

[_def_x_]

I was wondering what was causing my friend's XP English release to fail for some time according to her, even after today's update (rootcerts to v31). She said she was following my advice and still Unofficial, then I noticed 2 things...

The .md5 includes MRT and WUA (initially this is what threw me off), despite being commented out in the XP script (which I noticed later). Also, unless a user runs the common script (she hadn't) MRT and WUA will remain in the XP English release despite being signed without them. I had her manually remove the files and folders - release is now Official.

So, unless an XP English user adds the common script (they should), the release will show as Unofficial for the reasons I mentioned above (stray files). The fix (IMO), add the Delete commands to the XP English script - and update the .md5 file as well.

PreAction.FileDelete=autopatcher:modulesCriticalKB890830_x86_glb.apm
PreAction.FolderDelete=autopatcher:modulesCriticalKB890830_files
 
PreAction.FileDelete=autopatcher:modulesComponentsWindowsUpdateAgent_x86.apm
PreAction.FileDelete=autopatcher:modulesComponentsWindowsUpdateAgent_x64.apm
PreAction.FolderDelete=autopatcher:modulesComponentswindowsupdateagent30_files

If the user wants MRT and WUA they need only add autopatcher_common_.script. I'm not sure about the other OS releases...?

Obviously this wont affect a new user who downloaded XP English recently (after the files were commented out). Users who have maintained XP English for some time and have not added the common script likely will encounter this issue.

Edited by gUiTaR_mIkE, 20 October 2011 - 10:38 PM.

[dkdk_it]

I've not added any delete command in XP ENU script (and Seven, Vista, etc) because, if you select common release, these commands will delete any time MRT and WUA files.
To fix this issue, there are two ways:
- I can rename MRT and WUA apm files and directories
- the users can delete apm files and directories listed in previous post

I prefer the second option.