Windows 7 x64 - Error with prop sys.dll

[simcity]

Hi All,

My first post here. I have a Windows 7 x64 instance running as a VM under Parallels 9.0. It has been working faultlessly up until last week when I tried to enable sharing of the Bluetooth interface on my host Mac. That's when the problems started.

On subsequent reboot after the change I receive error dialog boxes on start-up prior to login, "Windows Logon: LogonUI.exe: - Bad Image" and the error message "C:Windows\System32\PROPSYS.dll is either not designed to run on this Windows or it contains an error.....etc, etc"

After logon, I am faced with a completely black screen with no start menu or toolbar visible. Explorer does not run and I can only get certain programs to run through Ctrl-Alt-Delete then using the windows task manger to get a command prompt up. Not good at all.

So I strongly suspect that Parallels has somehow screwed up the propsys.dll file, however I am unable to repair it using sfc /scannow.

Attached is a zipped copy of my CBS log folder. I have tried to run SFCFix.exe from this site, however this crashes.

Any ideas where to from here, other than a full Windows 7 re-install?

Many thanks

Sean

 

[simcity]

Cross posted my problem on the Parallels forums to see if any of the folks there have a resolution:

Parallels install hosed PropSys.dll--Can't login to Win 7 Now.

 

[tom982]

Hi simcity, welcome to Sysnative!

This should fix your SFC problem:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/simcity/SFCFix.zip

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
   
   
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

 

[simcity]

Hi Tom

Thank you very much for your help with this. Much appreciated.

Here is the output requested:

SFCFix version 2.2.0.0 by niemiro.
Start time: 2014-03-18 08:42:24.240
Using .zip script file at SFCFix.zip








Successfully processed all directives.
SFCFix version 2.2.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-03-18 08:42:25.457
----------------------EOF-----------------------

https://dl.dropboxusercontent.com/u/7628489/CBS.txt

 

[niemiro]

Hello simcity!

Tom's currently very busy, so you've got me instead :)

As you can probably see, there's not very much to see in that logfile. There are two possible reasons. Either the download became corrupt somewhere on route (I've just tested it, and the file's fine, but sometimes stuff just gets corrupt during transit), or there's a problem with the tool. I would like to first check the "lost in transit" possibility.

Can you please delete all of the SFCFix related files, script logfiles, etc. from your Desktop/downloads folder, then follow Tom's instructions exactly as before. We'll see if that fixes it, if not, we'll work something out :)

Thank you.

Richard