Eric, If you have installed Microsoft Security Essential=> uninstall,then if this didn't help use System Restore. I have same problem and settle with System Restore. Edit: kukubau,he cann't see Uninstall as me same before Restore.
I can't find the place where the SP backs up the files that it updates. There aren't any $aaaa folders created. I don't think you can delete the "service pack uninstall files" in Windows 7.
I am wondering the exact same thing.I would rather not uninstall my language pack in order to install this considering i have 80%+ of updates contained in SP1 Beta
There are over 200+ hotfixes included in this SP1, way more than those pushed through WU. And others undocumented.
I have it installed on a Win7 VPC x86. Before I installed the last one (in VPC) I created a "Restore point". For this new version I just restored to that prior to SP1 restore point & went back to that. Worked for me, I just completed the SP1 v.178 install where the earlier version was.
Performed a clean install of W7 x64 yesterday and directly applied this SP1 update. Since then I ran into a serious file/folder handle closing bug, which I can reproduce by for example: - browse to a random folder in Windows Explorer and then go one folder up and rename the "random" folder -> access denied - execute a random file, close the app and delete the "random" file -> access denied The files and folder handles in the System process seem to stay active for about 1 minute after I close the folder/file, which normally should be like.. instantly. Anyone else with SP1 v178 experiencing this issue?
mOBSCENE, I'm not seeing that on x86. When you say "go one folder up," is there any particular way you're doing that? It may matter. Did you install anything else on your clean install, such as AV (which does have an interest in everything you touch and may not be fully compatible yet)?
To go one folder up I either use the back button or Alt+Arrow Up, but it also happens within other applications. SpeedCommander for example, but my guess is this app uses parts of the Windows Explorer for browsing. Tried disabling my Avast! AV file shield, but same thing happens. It's too bad I cannot recall the exact moment I ran into this issue during installing all my drivers/apps. But it must be related to SP1, as it all worked fine in my pevious install (same apps/versions). And since I'm not running any other realtime shields/scanners, I'm betting it is something to be fixed by MS. Perhaps I should see if it also happens when running in Safe Mode. Thanks for your input. UPDATE: Crap, in safe mode the issue is not there! So, a compatibility issue with one of my apps it is. Let's hope more people will run into this issue, so we can compare on running processes.
Try having Process Explorer open when you see the lock condition. Then use its Find function to search on the filename that is locked but shouldn't be. Do you see anything unexpected?
Any way to get rid of the watermark? tried a couple of things posted on the net, but they didnt work.
I've made a Windows 7 Ultimate (32-bit and 64-bit) with SP1 Beta integrated, which i would like to share with you, but i don't want to store the iso files on any of those file-sharing sites (rapidshare, hotfile, etc) because most of them are slow and have restrictions unless you pay, so i don't know where to store the iso files, if anyone can help please let me know, thanks.
If we install this and next month final comes out. Will the final overwrite this or will it cause issues? i remember on vista it just overwrote. anyone know. I already installed but i created a restore point just incase before installing this . but besides doing a check disc on reboot everything went fine. up and running installed . not sure if placebo or not but seems a little snappier.Oh and what watermark are you talking about. i have nothing showing up on my desktop in that area.
There is no final coming out next month: it's the next beta that's coming out. The final isn't due until October or so. Uninstalling it is the recommended way to revert to where you were before (or an image). A restore point should be your last choice. I don't see the point of making an integrated before the final, particularly with the next beta less than a month away.