Hi there. I am trying to create a birthday field in a csv file, for the purposes of importing into Mailchimp. Mailchimp will only accept the date format as DD/MM, so I have created a custom cell format of dd/mm, but it is still not working.

I'd like to think it is not a case of upper v lower case as I can't change that and other people using Mailchimp are using this birthday field perfectly fine.

The only thing I can see after I change the cell format, is although in the cell itself it has the format DD/MM, in the formula bar at the top the date is still showing as DD/MM/YYYY. Is this the problem? How can I change this?

Given Mailchimp is a software used by millions around the world, I can only imagine I am doing something silly. Help!

Hola, hace unos días traté de calibrar el color con la herramienta "Calibración de Color de la pantalla" sin embargo, quiero regresar a la configuración de fábrica que trae Windows 10, pero no encuentro alguna opción que me lo permita, ¿hay alguien que tenga una solución para mi problema? Gracias! :D 

Whenever I boot up my laptop, Chromium attempts to open as a web page.  I removed this program from my computer in the control panel under "add/remove programs".  How can I get this program to be permanently removed from my computer?  Thanks for any advice.

I have installed Windows 10 Insider Preview 16215.1000 twice and both times, it totally loses my wireless network devises. I uninstall and reinstall and the wireless card then fails to initialize. Troubleshooter just reports problem with wireless networking device

Any ideas?

I I have a Dell Inspiron 16 gb and 24-3455, Its a desktop only 1 year old. I hardly have any downloads on this computer, it nearly new. I have windows 10 and I use the Edge to open up google and other sites. Recently when I open up a page it continues to load, over and over..... So I tried my Mozilla and same thing, continues to load. Please help!

onedrive.live.com这个一直上不去，连接超时，只能挂代理吗？

I have no problems attaching anything in an email, the only problem is it takes 24 hours for it to appear! For example, I just downloaded a bank statement and it appeared in my downloads and I was able to view it, but when I try to attach it to hotmail I can't upload it because I can't see it. I try to see it in all my files when i'm going through the attachment process and no luck. If I try again tomorrow, it will appear and I will be able to attach it no problem! This has been happening for quite a while and is very inconvenient when I have to get things done! Have asked around and no one has a clue... maybe you can suggest something. Thanks in advance :-)

Hello, I built a scheduling spreadsheet that adds up hours and calculates costs but I can't figure out how to create a formula that adds up hours and accounts for unpaid lunch breaks. I would like the formula to subtract a half hour IF any given shift is over 5 hours. This is the formula I have now:

=((C34-B34)+(F34-E34)+(I34-H34)+(L34-K34)+(O34-N34)+(R34-Q34)+(U34-T34))*24

For example, B34 is the time of end of shift and C34 is the time of beginning of shift. The formula adds up the hours worked for a week of any given employees schedule. Anyone know how I would do this?

家用版更新後未能登入

I downloaded I few games from Microsoft store and I cant seem to find them anywhere

I have two USB laser printers (Brother & Canon) installed & connected to a Win 8.1 TV stick which I want to use as a printer server to make the printers network discoverable.  The reason I'm doing this is there doesn't seem to be any 2 port USB printer network adapters out there which will do the job and this TV sick is more than capable to be used just for this and is low cost as well.

The Intel based Windows TV stick is connected to my router by Wi-Fi and a wired lan cable using a 3 port USB hub with ethernet lan connected to the USB port on the TV stick. The printers on the TV stick print OK directly as local printers and the TV stick is connected to my homegroup network. Printers are shared.

Also on my router (through a switch) my desktop Win 8.1 PC connects to both these 'networked' USB printers on the TV stick and were discoverable for set up.  They work fine for either a test print or normal print.

Also on my router is a legacy Win 7 desktop PC which also had no problem adding these printers to, nor printing to.

However, my Win 10 laptop connected to the router by wi-fi &/or wired lan despite seeing the TV stick on the network (along with all other PC's or network devices) it cannot see these USB printers connected to the TV stick and obviously it wont connect or print to them. ALL computers share the same homegroup with the same password.

I have tried all available options to try and add either of these pseudo 'network' printers (via the TV stick) to the Win10 laptop printer but to no avail and it should also be pointed out that a genuine network printer a wi-fi HP5520 does work on this Win 10 laptop.

That is the set up now here is the question - Why is it ONLY Win 10 that refuses to discover and add these 2 usb network printers when a Win 8.1 PC or Win 7 or Win 8.1 works fine ?

comment change mon compte microsof

Hello,

I reset my phone to have a fresh iOS and installed the new version of OneNote v16.2 170605

It worked for less than one day and now behaves the same a before and crashes immediately.

Any advice for this situation?

Thanks,

Office365のOutlookを使用しており、本日突然、特定の1つのフォルダのみ最新のメールしか表示されなくなりました。

そのフォルダはメールの特定の件名で分けているため、検索でそのワードを検索をかけたところ、過去のメールは検索に引っかかり表示されます。

ですので誤って削除をしたというのはなさそうです。

このフォルダを通常の状態（過去のメールも表示される）に戻すにはどうしたら良いでしょうか。

よろしくお願いします。

网页版和win10手机上都是按照“姓氏 名字”的顺序排列，在安卓版却是按照“名字 姓氏”排列，比如网页版和win10手机上是“张 三”，到了安卓版就变成了“三 张”，怎么解决？

Buon pomeriggio. Sono stato all'estero per alcuni giorni e mi sono correttamente collegato al wifi dell'hotel. Al rientro in Italia il mio surface pro 3 nn vede più alcuna rete wifi.

questo è il risultato dell'ipconfig:

Scheda LAN wireless Wi-Fi:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione: c.hoisthospitality.com
   Descrizione . . . . . . . . . . . . . : Marvell AVASTAR Wireless-AC Network Controller
   Indirizzo fisico. . . . . . . . . . . : 4C-0B-BE-10-0F-72
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Ho effettuato la ricerca delle cause dei problemi e mi ha dato un messaggio con scritto: "se connessi ad hot spot o a una rete di dominio, contattare l'amministratore di rete o altrimenti: 1. scollegare o spegnere il dispositivo 2. attendere 10 secondi dopo lo spegnimento di tutte le luci.

Proseguendo mi diche che il problema con il punto d'accesso e la rete wireless non è risolto.

Prima della partenza per l'estero funzionava tutto regolarmente, il pc è aggiornato così come la scheda di rete.

Come risolvo?

Salve,

dopo aver aggiornato windows 10 all'ultima versione (1073), non riesco più a connettermi ad internet (con chiavetta).

La diagnostica di rete non mi ha aiutato a risolvere il problema.

Come posso risolvere il problema?

Hallo liebe Community,

ich kenne es aus Windows 7, dass ich mir bspw. Verknüpfungen von SharePoint als Favorit ablege. Da sich die Bibliotheken im Namen oft gleichen oder wiederholen, habe ich die Verknüpfung unterhalb der Favoriten im Datei Explorer einfach immer passend umbenannt.

Unter Windows 10 heißt das Ganze ja jetzt Schnellzugriff. Das Ablegen von Verknüpfungen klappt weiterhin, allerdings nicht mehr das Umbenennen. Was ist jetzt hier der Weg, die Alternative?

20 Schnellzugriffe zu SharePoint namens "Dokumente" bringen mir ja nichts, ich möchte "Dokumente XY". "Kunden Dokumente" etc. daraus machen können.

Vielen Dank für eure Hilfe!

Steffi

I have a HP Elitebook that the touchscreen is redirecting my pointer to a bubble on the screen.  I've tried uninstalling the driver and restarting my computer.  It seems to work for a short period and then back to the bubble.  If I disable the touchscreen that works, but I would like to use the touchscreen.  Any suggestions?

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Desktop\053017-16770-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`04c1d000 PsLoadedModuleList = 0xfffff800`04e5f730
Debug session time: Tue May 30 14:46:43.429 2017 (GMT+8)
System Uptime: 0 days 0:14:04.662
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006a3ebb0, fffff80000ba0748, fffffa800e35b810}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+6f4c0 )

Followup: MachineOwner
---------