Search results

Since the AU, I can no longer disable the lock screen on my SB. I have edited the registry to include the NoLockScreen string and set it to 1. I have edited the group policies/admin options to disable the lock screen. Whenever the SB wakes from sleep, I have to dismiss the splash screen by...

I wish I had waited for the SB2.

I have read elsewhere that the sfc/scannow issue is related to there being more than one version of opencl.dll. The version on the SB is fine, but sfc expects to see a different version, so it throws an error. The sources I read said that it is not a concern.

I have had a couple of similar situations on my SB with Java based applications.

That's the part that bothers me too. It's one thing to have a few bugs at launch. It's entirely something different to make boastful performance claims at launch that you know are false. That's just dishonesty and deception in order to generate sales. I expect better of a company like Microsoft.

Any amount of testing at all would have revealed serious issues with the Surface Book. Microsoft chose to market the Surface Book notwithstanding these serious issues, while Panos Panay publicly gushed about its performance. Then it took six months to "pin point the issues faster". Not cool in...

This might be useful in a pinch, but I would say that experimenting to see if it will work falls squarely into the category of events where, shortly after, you say "What the heck was I thinking?"

It is very interesting to me that the volume of new posts regarding bugs and issues with the Surface Book has now dwindled to almost nothing. This reflects my own experience, where my SB is now functioning as I expected it to function and as it was advertised to function. That leaves me...

I have found that 95% of the time when I have a problem with connectivity to a wireless router, updating the firmware of the router fixes the issue. I also am not a Netgear fan, although I have had problems with routers from all the major manufacturers.

The 4/19 updates seem to have fixed my remaining SB issues. I can now, for the first time, use sleep and/or hibernate without any apparent problems. I am happy to finally have the product that I thought I bought in the first place. But I spent a lot of time and energy over the past six months...

I had the problem where the tip stopped working but the buttons still worked. Removing the pen battery, waiting 30 seconds, and putting it back together worked for me.

I have to admit that the ease with which posters and Microsoft support tell Surface Book users to reinstall Windows is extremely disturbing. This approach to problem solving takes me back to the earliest days of PC computing, when hardware vendors and others would routinely suggest such action...

^^^ That's the one I have too.

My updates installed fine, but many people are having issues with the updates - BSODs and failed updates. I would suggest waiting a day or two until these issues are resolved before triggering the update, if you have not updated already...

The Microsoft update page says that it fixes both the wake-from-hibernate auto-rotate issue and Windows Hello. There are also new video drivers. Here's hoping ... Edit: First test of wake-from-hibernate auto-rotate issue appears to have fixed the problem.

I think it depends on your tolerance for issues. If you can live with some of the issues that have been repeatedly posted about on this forum, and you do not intend to use the dock and/or multiple monitors, and you don't mind surfing the net for bug fixes and trying them, then the Surface Book...

It is really disappointing that some core functionality of the Surface Book is broken and Microsoft does not seem to be able (or willing) to fix it. A really expensive laptop that doesn't work as advertised is a failure IMO.

I have not had the wake-from-sleep problem in about two weeks now, but if I use hibernate I still get the no auto-rotate on detach problem. Accordingly, I have to completely disable hibernate (which I'm used to since hibernate has never worked properly).

In addition to disabling Fast Startup, make sure that hibernate is actually turned off. Even though FS is turned off, and all the power button/sleep button/lid close items are set to sleep instead of hibernate, hibernate can still come on automatically after a period of time. Go to Control...

Me too. Couldn't have been much to it - didn't even require a restart.