Jump to content

skay_baltimore

Members
  • Posts

    6
  • Joined

  • Last visited

skay_baltimore's Achievements

Newbie

Newbie (1/14)

  1. RecourceHacker is definitely simpler to use -- it only opens up the section that needs to be replaced. I just made the switch, and MSE runs without any problems. I'll have to wait until tomorrow morning, though, when the scan is set to run automatically. Checking the Event Viewer Admin logs and comparing the times of the errors, the auto scan seems to be what's triggering the error. Thanks again. I'll post back tomorrow with an update. So far, so good.
  2. Will do. (Is it a 50/50 shot whether to save it as ANSI or UTF-8? Or is one more likely to work than the other? I did back up the original. And if I happen to choose the one that doesn't work, will MSE give an immediate error message when I reboot or try to run a scan or update?) Thanks again. I can see the light at the end of the tunnel!!
  3. Fantastic. One last question: In your replacement code, it says processorArchitecture="amd64"; I'm using Intel i7, and in the code that I copied it says processorArchitecture="x86". Should I make that one change in your code, or leave it as it is? (And I'm glad you told me to make a backup copy of the .dll before I worked on it. I should have known that anyway.)
  4. Thanks. I'll give that a look, but I'm obviously a noob when it comes to this, so please bear with me. (I'm running Win 7 Pro 32-bit, btw). I re-opened the file using Notepad++, and set View to "wordwrap". Then I scrolled down and found the actual "English Language" section, vs the machine coded parts, and I think I found the part that needs to be replaced: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!-- Copyright © Microsoft Corporation --> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="5.1.0.0" processorArchitecture="x86" name="Microsoft.MSE.MSESysprep" type="win32" /> <imaging> <sysprepInformation> <sysprepModule moduleName="$(runtime.system32)\msesysprep.dll" methodName="DllSysprep_Cleanup" stage="cleanup"></sysprepModule> </sysprepInformation> </imaging> <description>Microsoft Security Client Sysprep module</description> <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!--Windows 7--> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> </application> </compatibility> <dependency> </dependency> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="asInvoker" uiAccess="false" /> </requestedPrivileges> </security> </trustInfo> </assembly> First of all, is this the exact section that's supposed to be highlighted, and then replaced with what you provided? Second, there are indentations in the section of the original .dll file, but not in yours; does that matter? Third, when I go to save it, does it matter what the Encoding section is set to? (It's currently set to encode to ANSI.) Fourth, do I have to turn off MSE, which is running all the time on my system, in order to be able to save it? Or do all of this in Safe Mode? Thanks.
  5. Hi. I'm having the exact same problem, so I installed Notepad++ and opened up the .dll file in question. However, what I got when I opened up that file looked nothing at all like what you posted -- it looked like a bunch of coded symbols, not the easy to read words you show in your replacement file. The encode option in Notepad++ was set to ANSI. I tried setting it to UTF-8 but that didn't help. This is all new to me, and I didn't want to mess anything up, so I just closed it without saving. Could you please let me know what I did wrong, and/or what I need to do correctly to get the file changed and saved? Also, do I have to do this in safe mode or turn off MSE before making the change to the .dll? Thanks.
×
×
  • Create New...