Search results

I'm not sure if you can toss the image on another machine or not with Windows. You certainly can with Macs, as I've done it many times. I don't think the serial number would matter, as the OS detects that from the firmware.

I would get rid of Kapernsky, with or without the Surface Pro, Pen, etc.. The built in virus protection in Windows 10 is sufficient and the 3rd party virus software is more trouble than its worth, and I don't believe it provides any additional security for the trouble.

Why would you be moving the mouse when your Surface is in your bag asleep? I've not had mine wake up in my bag and did travel with it last week.

I ended up staying with the i5... still running great. Did my first travel with it last week and was quite pleased with everything... usability, performance, battery life, inking, and portability.

You are right, I don't understand all these problems that are unique to you. I won't dispense any more advice to you, so best of luck.

Well my conclusion is that's your problem. You had a pure factory state, the way Microsoft intended it for the Surface, when you opened the box. I'm guessing something in your OEM image is not just right, driver wise, for the Surface. I can see possibly doing an image if you bought some no...

Wow, that was quick! You gave up photography because FB sucked so bad! :eek: If you decide to give it a go again, I would make a suggestion. I am in a very similar situation as you. I used to do sports photography as a business, so I have the equipment, experience, and will to get better...

I think the key here is that he re-imaged the machine before he used it. One of the problems he reported he's seeing on his SP4 as well. Sounds like his OEM Windows 10 image may have some Surface driver problems. I've never felt a need to reimage a machine I just took out of the box before...

Where did you get the factory OEM image? I didn't re-image mine and I'm not seeing these problems. Maybe as was suggested by @hughlle, you could return it and try using the next one without the re-image. As the saying goes, "if it ain't broke...".

I'm not blaming anything... I'm just making suggestions. You have several problems that seem to be unique to you, as I've not seen anyone else reporting any of them on any of the forums that cover the nSP. That doesn't sound like factory configuration. When you say the first thing you did was...

Sounds like you have a number problems that are unique to your machine, and also sounds like you've made some configuration changes that the average user probably isn't doing. Might be worth doing a reset and starting over.

I have not seen any of these problems... may be something you've loaded on your machine. In another thread you mentioned VMWare, and I can logically see how it could potentially contribute to all of these since its doing hardware level stuff.

Not seen anything like this, so may be something about your configuration. You mentioned running VMWare, and that could be causing the problem.

I don't think that TRIM is something you need to initiate. It should be set to on, and it will then take care of itself, was my understanding. You can run "fsutil behavior query DisableDeleteNotify" at the command line and if it returns that its set to zero for NTFS, then it is running TRIM...

Did you initiate the defrag, or did it do on its own? How did you know it was trying?

I've had mine for a month and use the pen daily. I've not had any problems like you described. This is the nSP with nSP Pen.

I experienced it once last week, and hadn't had it happen at all the 3 prior weeks I had it.

I don't think the i5 is going to "grind to a halt" in 3 years. I've been using an i5 Mac Mini for over 5 years and it hasn't ground to a halt. Unless you are planning on doing something dramatically different in 3 years that will require a lot more CPU power, it should be fine. I bought the...

Did you swap it out?

Mine scrolls side to side with 2 fingers, and I didn't do anything to enable it. What application are you in? I just tested it in Outlook.