BetaTime

I wanted to know, if i change adaptive brightness from ON to OFF, when does system replicate the same? just after changing or it requires restart? More...

I plan to create 2 storage spaces, 1 for my active data (mostly pictures and videos) and 1 for backup. Should I create 1 storage pool for both my data and backup storage spaces? Or, should I create 2 separate storage pools, 1 for each storage space? More...

Hello all. I have spent a good part of my day today assisting one of my helpdesk guys with a project that he is working on involving customizing the start menu layout for Windows 10, locking it down, and deploying it to a subset of my user base. We have followed this and several similar articles with no luck: https://blogs.technet.microsoft.com/deploymentguys/2016/03/07/windows-10-start-layout-customization/ He created a brand new profile on a fresh Windows 10 workstation and ran the Export-StartLayout Powershell cmdlet to export the config to XML. We built a GPO and enabled both the user and computer policies for Policies > Administrative Templates >Start Menu and Taskbar and configured the Start Layout policy to enabled with the file path set to where we put the XML (we put it in the GPO in sysvol so users can easily get to it to read it.). Long story short, we tested this and it is not working. GPRESULT -R and RSPO.MSC confirm that all parts of the policy are being applied and it effectively locks the start menu from further customization (as we wanted) but it's not updating the layout. We can reach the script through UNC but it just doesn't seem to want to work. Any suggestions? More...

Hello, is it possible to unpin pinned apps from the start menu via Powershell? I am only looking for a Powershell solution (not GPO oder whatever). The Windows version is Windows 10, version 1803. More...

Hello! We have several system, which sporadically (about 1 in 10 tries) get a bluescreen when the touch screen is first touched on the windows logon screen (when "pushing" to screen up to reveal the password box). We have updated Windows, the graphics drivers and the touch screen drivers to the newest versions with no luck, and are a little stumped. How would we troubleshoot this situation? We have uploaded a minidump of this crash to https://we.tl/t-SqeucyZZuw. Note that this minidump may not reflect the driver updates, but nothing changed after performing them. A first WinDbg analysis follows. Thank you and kind regards Jens Microsoft ® Windows Debugger Version 10.0.17134.1 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Manager\Desktop\082318-4109-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 14393 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 14393.2363.amd64fre.rs1_release.180625-1741 Machine Name: Kernel base = 0xfffff801`d4802000 PsLoadedModuleList = 0xfffff801`d4b08140 Debug session time: Thu Aug 23 09:10:35.041 2018 (UTC + 2:00) System Uptime: 0 days 0:09:23.770 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ........................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000094, ffff9f5dc086848b, 400, fffffffffffffc00} Probably caused by : win32kbase.sys ( win32kbase!rimConvertCoordinatesWithRounding+37 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000094, The exception code that was not handled Arg2: ffff9f5dc086848b, The address that the exception occurred at Arg3: 0000000000000400, Parameter 0 of the exception Arg4: fffffffffffffc00, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 14393.2363.amd64fre.rs1_release.180625-1741 SYSTEM_MANUFACTURER: To be filled by O.E.M. SYSTEM_PRODUCT_NAME: To be filled by O.E.M. SYSTEM_SKU: To be filled by O.E.M. SYSTEM_VERSION: To be filled by O.E.M. BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 4.6.5 BIOS_DATE: 03/24/2016 BASEBOARD_MANUFACTURER: INTEL Corporation BASEBOARD_PRODUCT: ChiefRiver BASEBOARD_VERSION: To be filled by O.E.M. DUMP_TYPE: 2 BUGCHECK_P1: ffffffffc0000094 BUGCHECK_P2: ffff9f5dc086848b BUGCHECK_P3: 400 BUGCHECK_P4: fffffffffffffc00 EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero. FAULTING_IP: win32kbase!rimConvertCoordinatesWithRounding+37 ffff9f5d`c086848b 48f7f9 idiv rax,rcx EXCEPTION_PARAMETER1: 0000000000000400 EXCEPTION_PARAMETER2: fffffffffffffc00 BUGCHECK_STR: 0x1E_c0000094 CPU_COUNT: 4 CPU_MHZ: 958 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3a CPU_STEPPING: 9 CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: JADEV ANALYSIS_SESSION_TIME: 08-23-2018 11:09:19.0971 ANALYSIS_VERSION: 10.0.17134.1 x86fre EXCEPTION_RECORD: fffff0cfaee043a8 -- (.exr 0xfffff0cfaee043a8) ExceptionAddress: d58c3d0727480400 ExceptionCode: 0c69f021 ExceptionFlags: 4cb00001 NumberParameters: 659555328 Parameter[0]: d58c3d0727580400 Parameter[1]: d58c3d0727600400 Parameter[2]: d58c3d0727680400 Parameter[3]: d58c3d0727700400 Parameter[4]: d58c3d0727780400 Parameter[5]: d58c3d0727800400 Parameter[6]: d58c3d0727880400 Parameter[7]: d58c3d0727900400 Parameter[8]: d58c3d0727980400 Parameter[9]: d58c3d0727a00400 Parameter[10]: d58c3d0727a80400 Parameter[11]: d58c3d0727b00400 Parameter[12]: d58c3d0727b80400 Parameter[13]: d58c3d0727c00400 Parameter[14]: d58c3d0727c80400 TRAP_FRAME: ffff9f5dc0871a00 -- (.trap 0xffff9f5dc0871a00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=ccc35f40c4834858 rsp=7504a800000a3c80 rbp=24748b48fff33c34 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 ov dn di ng zr ac pe nc 8b4c:ccc35f40`c4834858 ?? ??? Resetting default scope BAD_STACK_POINTER: 7504a800000a3c80 LAST_CONTROL_TRANSFER: from fffff801d48a4f4d to fffff801d495d9b0 STACK_TEXT: ffffb580`667a3428 fffff801`d48a4f4d : 00000000`0000001e ffffffff`c0000094 ffff9f5d`c086848b 00000000`00000400 : nt!KeBugCheckEx ffffb580`667a3430 fffff801`d496db02 : fffff0cf`aee043a8 ffffb580`6858cbc0 ffff9f5d`c0871a00 ffffd58c`00000000 : nt!KiDispatchException+0x22d ffffb580`667a3ae0 fffff801`d4967ac6 : ffffb580`00000000 00000000`00000010 00000000`00000000 ffff9f87`33b32d00 : nt!KiExceptionDispatch+0xc2 ffffb580`667a3cc0 ffff9f5d`c086848b : ffff9f5d`c08678a3 fffff801`d4af0000 ffff9f5d`c07ca821 ffffb580`3de03e00 : nt!KiDivideErrorFault+0x2c6 ffffb580`667a3e58 ffff9f5d`c08678a3 : fffff801`d4af0000 ffff9f5d`c07ca821 ffffb580`3de03e00 ffff9f5d`c08678ce : win32kbase!rimConvertCoordinatesWithRounding+0x37 ffffb580`667a3e60 ffff9f5d`c08680c8 : ffffffff`ffffffff ffffb580`667a3ecc ffff9f14`40a37010 ffff9f14`40b57990 : win32kbase!RIMConvertPointCoordinates+0x3b ffffb580`667a3ea0 ffff9f5d`c08674af : ffff9f14`40b57990 ffff9f14`40a37010 ffff9f14`00000fff ffffb580`667a40d0 : win32kbase!RIMTransformPhysicalPointToScreen+0x164 ffffb580`667a3f10 ffff9f5d`c087263c : ffff9f14`00000000 ffff9f14`40b57918 ffff9f87`33912360 00000000`55c8c1f9 : win32kbase!RIMApplyTransforms+0x107 ffffb580`667a3f70 ffff9f5d`c0871f0e : 00000000`00110000 ffff9f87`34edb010 00000000`00000010 00000000`00000008 : win32kbase!rimTransformGeometry+0x54 ffffb580`667a3fb0 ffff9f5d`c08722ff : ffff9f87`34edb010 ffff9f14`40b57000 ffff9f87`347eff10 ffff9f5d`00000008 : win32kbase!rimPopulateContactFrameData+0x20e ffffb580`667a4050 ffff9f5d`c087052b : 00000000`55c8c1d8 ffffb580`00000001 ffff9f87`347eff10 00000000`00000005 : win32kbase!rimProcessPointerDeviceContact+0x157 ffffb580`667a4120 ffff9f5d`c086f69c : ffff9f87`33910000 ffff9f5d`00000000 00000000`00000001 00000000`00000001 : win32kbase!rimDoProcessAnyPointerDeviceInput+0x29f ffffb580`667a41f0 ffff9f5d`c0828d5a : ffff9f87`33912360 ffff9f87`34c65340 ffff9f87`34c65340 ffff9f87`34c65340 : win32kbase!RIMProcessAnyPointerDeviceInput+0xf4 ffffb580`667a4230 ffff9f5d`c07a33d2 : 00000000`00000001 ffff9f87`33912360 00000000`00000000 00000000`00000000 : win32kbase!rimProcessDeviceBufferAndStartRead+0x86c46 ffffb580`667a4280 fffff801`d485485a : 00000000`00000001 ffff9f87`34c657c0 ffffb580`667a4330 00000000`00000000 : win32kbase!rimInputApc+0xc2 ffffb580`667a42e0 fffff801`d4851f54 : 00000000`00000100 00000000`00000000 ffff9f87`00000000 00000001`0d16d021 : nt!KiDeliverApc+0x22a ffffb580`667a4370 fffff801`d485180f : ffff9f87`33ae36f0 ffffb580`6858cbc0 ffff9f87`34c65900 fffff801`d4802000 : nt!KiSwapThread+0x364 ffffb580`667a4420 fffff801`d48ec1e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000101 : nt!KiCommitThreadWait+0x14f ffffb580`667a44c0 fffff801`d48ebcb8 : 00000000`00000000 ffffb580`667a48a0 ffffd58c`00000000 ffff9f87`31603000 : nt!KeRemoveQueueEx+0x2f0 ffffb580`667a4540 fffff801`d4c88dcb : 00000000`746c6644 ffffb580`667a46e0 ffff9f87`34b272b0 00000000`00000000 : nt!IoRemoveIoCompletion+0x98 ffffb580`667a4670 fffff801`d496d503 : ffff3f3e`178333fa 00000000`001f0001 ffff9f87`00000000 00000000`00000201 : nt!NtRemoveIoCompletionEx+0xeb ffffb580`667a47b0 fffff801`d49612e0 : ffff9f5d`c0423311 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 ffffb580`667a49b8 ffff9f5d`c0423311 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9f14`40005750 : nt!KiServiceLinkage ffffb580`667a49c0 ffff9f5d`c079e7c0 : 00000000`00000000 ffff9f87`34b272b0 00000000`000001a4 fffff801`00000002 : win32kfull!UserProcessDwmInput+0x1a1 ffffb580`667a4a60 ffff9f5d`c079e63e : 00000000`00000000 00000000`00000000 00000000`000001bc 000001e8`8b2e5d00 : win32kbase!CInputManager::DwmInputThread+0xcc ffffb580`667a4ac0 fffff801`d496d503 : ffff9f87`34c657c0 ffffb580`667a4b80 000001e8`8b2e5d00 00007ff8`7e017d70 : win32kbase!NtCompositionInputThread+0x4e ffffb580`667a4b00 00007ff8`81b23464 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 000000b0`080ffeb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`81b23464 THREAD_SHA1_HASH_MOD_FUNC: 4556c4b3b180cbccf11edf360400d5571235d2a8 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 22b0f96a87ab01bec9f323b0762b2f79e5465231 THREAD_SHA1_HASH_MOD: ab6963d1aa9a75bca2aa1382de2ace7e36e8b606 FOLLOWUP_IP: win32kbase!rimConvertCoordinatesWithRounding+37 ffff9f5d`c086848b 48f7f9 idiv rax,rcx FAULT_INSTR_CODE: baf9f748 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: win32kbase!rimConvertCoordinatesWithRounding+37 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32kbase IMAGE_NAME: win32kbase.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5ae4091b IMAGE_VERSION: 10.0.14393.2273 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 37 FAILURE_BUCKET_ID: 0x1E_c0000094_STACKPTR_ERROR_win32kbase!rimConvertCoordinatesWithRounding BUCKET_ID: 0x1E_c0000094_STACKPTR_ERROR_win32kbase!rimConvertCoordinatesWithRounding PRIMARY_PROBLEM_CLASS: 0x1E_c0000094_STACKPTR_ERROR_win32kbase!rimConvertCoordinatesWithRounding TARGET_TIME: 2018-08-23T07:10:35.000Z OSBUILD: 14393 OSSERVICEPACK: 2363 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2018-06-26 05:06:53 BUILDDATESTAMP_STR: 180625-1741 BUILDLAB_STR: rs1_release BUILDOSVER_STR: 10.0.14393.2363.amd64fre.rs1_release.180625-1741 ANALYSIS_SESSION_ELAPSED_TIME: 257a ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1e_c0000094_stackptr_error_win32kbase!rimconvertcoordinateswithrounding FAILURE_ID_HASH: {387a1d0a-87b5-edfb-4ebf-99288e0f834c} Followup: MachineOwner --------- More...

Event ID 916 has always been a prominent event in the Application log, for about as long as I've had Windows 10. I've never had cause for concern over it, though it does take up quite a bit of real estate. However, since purchasing my first Microsoft game (Sea of Thieves), I have been able to correlate freezes and eventual crashes to these events. There are a number of different instances of the event, from "DllHost" to "svchost" to "SettingSyncHost" claiming to be responsible. Sometimes there will be a flood of instances right in a row (usually during gameplay and just before a freeze). I have done a lot of research online about this event, as well as this "EseDiskFlushConsistency" flag that says it's enabled. An example of the verbiage is here: SettingSyncHost (7524,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000. And, while there are no shortage of questions on Microsoft, Technet and numerous third party forums, there are apparently ZERO solutions. No one, not even Microsoft has an answer or an explanation on how to disable this service or if it can be disabled at all. At least, as far as they're willing to offer up. Some suggestions have been to disable any Qualcomm hardware or disable auto-trim for SSDs. Unfortunately, neither of these has worked. At this point, any explanation other than "this warning is harmless" from Microsoft themselves would be welcome. What is ESENT? What is EseDiskFlushConsistency? Can EseDiskFlushConsistency be disabled? If so, how? Can the application and/or hardware utilizing this service be determined? If so, how? Does ESENT have any relationship with the Software Protection service? Any light that can be shed on this issue would be WONDERFUL! I know that I'm not the only one experiencing these problems, as evidenced by a simple search for Event ID 916, EseDiskFlushConsistency or ESENT. I will gladly post any system information that may be helpful to the cause, but at this point in my research, I've come to believe that this issue is specific to Windows 10. Thank you in advance! More...

Hi, i hope you can help. I have been trying all day to suss this and i just cannot for the life of me get this to work. I work in a school and our students cannot/should not have access to search app's on the start menu. Firstly, can we disable apps from being searched on the start menu? (attached a screenshot below) https://imgur.com/9gaeBL3 So far i have Disabled the search 'box' on the task bar Disabled cortana via GPO - Even though this does nothing from what i can tell. Added a disallowed file rule in the path of cortana within c:\windows\systemapps - This works! However when a user logs in, the start menu is not clickable for the first time a user clicks the bottom left button. Although if the user closes the start menu and re-opens it. The start menu works totally fine. Another screenshot here to show the start menu greyed out: https://imgur.com/7MZZVmO In short, all i would like to do is remove APPS from the start menu! or un-grey out the screen when a user logs on. Thanks, Joe. More...

Hi i have an aunts old computer that she wants to start using but want the OS to act more like windows XP. My first step was hopefully to install win10 and worry about tweaking it to act like XP/7. what are my options if I cant upgrade for free Ill just try and work with 8.1 More...

Hi Techies, We're looking for a way where we can prevent users to access settings icon from Touch keyBoard. Is there any way to disable this? Please let me know!! https://social.technet.microsoft.com/Forums/getfile/1308106 Thanks! More...

This forum contains an archive of threads and posts for operating systems that Microsoft has declared EOL ( End of Life ). This is a read only collection of old threads.

Re: Maine to skip Vista No big deal. Vista is still doing well in the market.

Re: New PC/No OS XP SP3 & Vista SP1 Go with Vista x64. That is what I use and love it.

Re: Hello Welcome to the community.

Re: Aloha howdy and welcome.

Re: Hi! Welcome to the community Asoons.

Re: Product review: Visual Studio 2008 advances with few missteps - InfoWorld Welcome Fred. I corrected the url in your post. You had a \ in the url instead of /.

Re: Evaluation Copy??? Once you uninstall SP1 that will disappear from the desktop.

Re: Aero Theme will not stay set and so cannot turn on Aero Have you installed any software lately? While rare now that Vsta has been out for a while certain software would cause Vista to disable Aero. I remember Java used to do that

Re: hello - how do I post on site? You're good to go. Spam filters got a bit overzealous.

Re: Quick Hello - MCSE / AD / Exchange The spam filters got a little overzealous. I have approved your posts and you sould have no problems posting again. Sorry about the inconvenience. Welcome to the site

Re: Hello Hello and welcome.

Re: Hello Hello and welcome.

Re: Presenting myself Welcome to MS OS.

Re: Just saying hello Hello to you and welcome to the community.

I have changed the look of the site. Many thanks to VistaBoard for making this style available. Hope all of you like it.