New Folder

[tobyhutton1234]

Everytime I create a new folder and then name it to whatever and then press enter

I get the following follow error:

--See Attachment--

Then folder just changes it name.

Whats up with this.

 

[Espio]

Are you creating this folder locally or remotely?

 

[tobyhutton1234]

Locally

 

[Espio]

Cool, thats good. Try seeing if the location is the problem, try it in different locations (I.E. Where are you trying to create the folder, and can you try somewhere else and see if it works?)
Then, also try it in safe mode, see if that works. (Safe Mode doesn't support networking)
Come back with the findings.

And now I must rest. Good luck on your search. I wish teamviewer could be used in this instance. I'll be back in 8 hours

 

[seavixen32]

You can troubleshoot a problem using a Windows Clean Boot procedure, but it is rather long-winded:

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

You could also try creating a new account to see if the problem still occurs.

If you can't replicate the issue when you boot into safe mode you may have a corrupted driver, a corropted update or a virus of some sort.

 

[tobyhutton1234]

I'm still getting the same error.

It's only started since I Installed SP1 yesturday. mmm

 

[seavixen32]

In that case, you can uninstall SP1 to check out your supposition.

If it is the cause then we'd need to find out why.

 

[Brink]

Hello Toby,

You might see if downloading and merging the Folder option in the tutorial below may be able to help. It will restore the default associations for folders including "New Folder".

http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

Hope this helps,
Shawn

 

[tobyhutton1234]

Thanks your post and advice here.

I had removed service pack 1 and this fixed the issue.

Now I need to investigate why SP1 has done this.

I know there have been some issues that people have had with SP1 like blue screens etc etc.

 

[seavixen32]

It seems SP1 has been rather problematic for quite a few users.

 

[tobyhutton1234]

Yes it has, I've also noticed Server 2008 R2 has problems with it too.